cladding-init
Use only when the user explicitly names Cladding and asks to initialize, adopt, or refresh it; never use for an ordinary project…
@qwerfunchInstall SkillDevelopment
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
Claude Code
$ npx -y skills add purpleeddy/cladding --skill status --agent claude-code
Codex
$ npx skills add purpleeddy/cladding --skill status -a codex -y
Cursor
$ npx skills add purpleeddy/cladding --skill status -a cursor -y
Gemini CLI
$ npx skills add purpleeddy/cladding --skill status -a gemini-cli -y
GitHub Copilot
$ npx skills add purpleeddy/cladding --skill status -a github-copilot -y
OpenCode
$ npx skills add purpleeddy/cladding --skill status -a opencode -y
Windsurf
$ npx skills add purpleeddy/cladding --skill status -a windsurf -y
SKILL.md
status.SKILL.mddescription: 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
Stats
16
Stars
4
Forks
Maintained
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
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.
1619 skills6 agents1 MCP
Stars on GitHub
Momentum
- stars in total
- 16
Other skills on cladding.
@qwerfunchInstall Skillblind-author
Impl-blind test/oracle author — writes conformance tests from a spec-only brief. Tool-restricted by definition (no…
@qwerfunchInstall Skillchangelog
Render release notes / a changelog from the cladding spec. Use when the user asks for release notes, a changelog, 릴리즈 노트, 변경 이력,…
@qwerfunchInstall Skillcheck
Run every Iron Law stage and the drift detector suite. Use when the user wants the full project health snapshot, a CI gate, or to…
@qwerfunchInstall Skillcheckpoint
Record a feature checkpoint event pinning the current git HEAD plus a spec digest, so a later rollback can restore the exact…
@qwerfunchInstall Skillclarify
Advance Cladding onboarding after the user answers a pending product question. Use the MCP prepare/apply flow, preserve the…
@qwerfunchInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about status.
- Which coding agents can use status?
- status installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.