Skip to content
Development
Skill

/status

Render the feature × stage integrity matrix — every feature vs every Iron Law stage with pass/skip/fail markers. Use when the user wants a project-wide status board, a release-readiness view, or to spot which features are still behind which stage. Activate only when the

From plugin
cladding
1619 skills6 agents1 command1 MCP
Install
$ npx -y skills add qwerfunch/cladding --skill status --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/status

Context preview

The summary Claude sees to decide when to auto-load this skill.

Render the feature × stage integrity matrix — every feature vs every Iron Law stage with pass/skip/fail markers. Use when the user wants a project-wide status board, a release-readiness view, or to spot which features are still behind which stage. Activate only when the

SKILL.md

status.SKILL.md
description: Render the feature × stage integrity matrix — every feature vs every Iron Law stage with pass/skip/fail markers. Use when the user wants a project-wide status board, a release-readiness view, or to spot which features are still behind which stage. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.

Cladding status (formerly `panel`)

Run `clad status` from the project root. Renders an ASCII matrix:

  • Rows: features (business titles by default; raw ids with `--internal` — legacy `F-NNN` for historical features, and current generated `F-<hash8>` identifiers).
  • Columns: 15 Iron Law stages.
  • Cells: pass · skip · fail · not-yet-attempted.

Use this after `clad check` to see *which features* failed *which stages* at a glance, not just the aggregate exit code.

clad status
clad status --internal
Ships withcladding

For an organization to trust AI with its code, three things must hold — trust, traceability, and stability at scale. cladding wraps your AI coding agent: your intent goes in before it writes, and the result is verified against your spec after, so those three are earned, not assumed. First L4 implementation of the Ironclad standard.

Get the whole plugin

Other skills on cladding.