AI Agent Workflow Collection

Create the next-numbered Architecture Decision Record in the project's docs/ADR/ directory, using the Nygard format (Status, Context, Decision, Consequences). Use when the user runs /cadence-adr, asks to write an ADR, document an architectural decision, or capture a judgment call.

Auto-loaded helper for writing Architecture Decision Records in the Nygard format. Activates when the user mentions ADR, architectural decision, judgment call, design rationale, or asks how to document a non-obvious decision. Provides the Nygard format and ADR-writing guidance.

Generate a compliance report mapping the project's Cadence artifacts to industry standards (NIST SSDF v1.1 or ISO/IEC 25010:2023). Use when the user runs /cadence-compliance, asks for a compliance report, asks how the project aligns with NIST SSDF, or asks for an ISO 25010 coverage roll-up.

Auto-loaded reference for the Cadence framework's patterns, definition of done, and role specs. Activates when the user asks about patterns, definition of done, DoD, role specs, narrow providers, optimistic mutation, the four-layer model, or other Cadence framework concepts.

Scaffold the Cadence framework into the current repository. Use when the user runs /cadence-init or asks to set up the Cadence framework, install patterns, bootstrap docs/ADRs/verify scripts, or initialize the four-layer development framework in a repo.

Fill in the Cadence team launch template for a new feature, render the launch prompt, and optionally spawn four coordinated subagents (data engineer, feature engineer, tester, reviewer). Use when the user runs /cadence-launch or asks to kick off a feature with a Cadence team.

Drive the Cadence retrospective protocol after a team run. For each observed issue, map to one of the four fix layers (Patterns, Process, Automated gates, Launch) and emit specific patches. Use when the user runs /cadence-retro, asks to do a retrospective, runs a post-mortem on work just completed, or asks how to capture lessons learned.

Auto-loaded helper for running Cadence retrospectives. Activates when the user mentions retro, retrospective, post-mortem, lessons learned, what went wrong, framework finding, or asks for a structured reflection on completed work. Provides the four-layer fix mapping and the proper output format.

Run the Cadence verify pipeline (format / lint / boundary check / test) using the project's cadence.yaml configuration, then render the output as a Definition-of-Done aligned checklist. Use when the user runs /cadence-verify, asks to verify the project, or asks whether work is done.