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
Skill Claude CodeCodex
Add a new endpoint / MediatR command or query / handler / service the way this .NET codebase already does it. Use when building an API surface, a CQRS handler, a controller, a validator, or a DI registration in a .NET / Clean Architecture repo. Finds the one canonical example and mirrors its layering, validation…
MCKRUZ/intent-driven-development
Skill Claude CodeCodex
Add a new endpoint / route / use case / service the way this Node + TypeScript codebase already does it. Use when building an API surface, a request handler, a validator, a port/adapter, or a container registration in a Node/TypeScript repo. Finds the one canonical example and mirrors its layering, validation, error…
MCKRUZ/intent-driven-development
Skill Claude CodeCodex
Add a new module / CLI command / service function / loader the way this Python codebase already does it. Use when building a public surface, a command entry point, a data loader, a validator, or a new package module in a Python / uv repo. Finds the one canonical example and mirrors its layering, typing, error model…
MCKRUZ/intent-driven-development
Skill Claude CodeCodex
Add a new endpoint / handler / service the way this codebase already does it. Use when building an API surface, a CQRS handler, a controller, or a service registration. Finds the one canonical example and follows it exactly — so agents reuse the established pattern instead of inventing a new one each run.
MCKRUZ/intent-driven-development
Skill Claude CodeCodex
The team's bug-fix procedure: reproduce with a FAILING TEST first, then fix, then prove the test passes. Use whenever a bug is reported. Do not start by patching — start by reproducing. For deep root-cause hunts, invoke the debugger agent from inside this procedure.
MCKRUZ/intent-driven-development
Skill Claude CodeCodex
Build a golden set for an agentic (LLM-powered) spec — the acceptance criteria for probabilistic behavior. Use when a spec's deliverable is an agent/prompt/tool and needs evals before build, or when adding cases from a production failure. Produces a versioned golden-set.yaml under eval-datasets/specs/ /, referencing…
MCKRUZ/intent-driven-development
Skill Claude CodeCodex
Open a spec's PR correctly: the right branch, a conventional-commit title, a body that maps the diff to the spec's acceptance checks with a test plan, and the spec file included in the diff. Use when a change is ready to push for review.
MCKRUZ/intent-driven-development
Skill Claude CodeCodex
Turn a backlog story into a Definition-of-Ready spec at specs/NNNN-name.md. Use when the user wants to "write a spec", "make this story ready", or start a feature. Enforces the vague-line test on every acceptance check and assigns a risk tier. Use BEFORE delegating any build — no spec, no build.
MCKRUZ/intent-driven-development
Skill Claude CodeCodex
Write tests that encode WHY behavior matters, mapped to a spec's acceptance checks. Use when adding tests for a feature or reproducing a bug. For bug fixes, write the failing test FIRST. Targets the team's coverage bar on new code.