Menu
Use when implementing behavior from an approved plan with test-first or regression-test-first development.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when adding, changing, or reviewing MCP servers, agent tools, provider integrations, credentials, scopes, or tool approval behavior.
Use when converting a product spec, use case, or PRD into a concrete implementation plan before code changes.
Use to review a diff against repository contracts, specs, docs, tests, and architecture boundaries.
Use after incidents, regressions, repeated review findings, or completed features to convert lessons into durable factory improvements.
Use when a task requires meaningful implementation. Research the repo, inspect docs/specs, and create a concrete plan before editing code.
Use when splitting complex work into independent subagent tasks with clear ownership, evidence, and integration responsibilities.
| name | tdd-implementation-loop |
| description | Use when implementing behavior from an approved plan with test-first or regression-test-first development. |
AGENTS.md, the active plan, and the relevant spec.Return changed files, tests added, validation commands, and any behavior that remains untested.