Intent Driven Development — the delivery standard: how our pods build software with AI agents, phase by phase, with a full worked example
MCKRUZ/intent-driven-development
Agent
System-design and architectural decisions: new services, cross-cutting changes, scaling and data-model calls, public API contracts. Use for HIGH-risk design work BEFORE a spec is built against it. Produces a design with trade-offs and a recommendation — it does not write code.
MCKRUZ/intent-driven-development
Agent
Fixes build, compile, type, and lint errors with minimal diffs. Use PROACTIVELY (auto-spawn) the moment a build or lint step fails. Gets the build green fast — no architectural changes, no scope expansion. Pairs with the Stop hook, which won't let a turn end on a broken build.
MCKRUZ/intent-driven-development
Agent
Root-causes a failing test, exception, or wrong behavior via hypothesis elimination, in an isolated context. Use when the cause isn't obvious. Returns a distilled diagnosis + a minimal reproduction — it does not apply the fix (that happens under the bug-fix procedure).
MCKRUZ/intent-driven-development
Agent
Grades a change against its spec, check by check, and posts an advisory verdict. Use before a PR is approved, or invoke locally before pushing. The grader NEVER grades its own work — it runs in a fresh context and did not write the code.
MCKRUZ/intent-driven-development
Agent
Produces an implementation plan for a spec before code is written. Use for any MEDIUM or HIGH spec, or any feature touching 5+ files / a new service. Returns a sequenced plan with files to touch, order of changes, risks, and unknowns — it does NOT write code.
MCKRUZ/intent-driven-development
Agent
Reviews changes on gated paths or HIGH-risk specs for security defects. Use PROACTIVELY when a change touches auth, identity, payments, PII, migrations, infra, the pipeline, or prompt/model/tool definitions. BLOCKS on a HIGH-severity finding; advises otherwise.
MCKRUZ/intent-driven-development
Agent
Reviews user-facing Angular changes for UX quality: every state exists (loading, empty, error, success), accessibility basics hold, components follow the codebase's existing patterns, and the flow works end-to-end. Angular-aware — also catches the framework's own failure modes. Use PROACTIVELY when a change adds or…