メニュー
Test-driven development for one feature slice or bug fix. Use when Codex should work red-green-refactor, add behavior-focused tests, protect public interfaces, or turn a repro into a regression test during implementation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Shared vocabulary and decision process for designing module interfaces and test seams. Use when Codex needs to decide where a seam belongs, judge whether a module is deep or shallow, design an interface that serves slicing and acceptance, or make code easier to test and navigate.
Maintain a repository's domain vocabulary and architecture decision records. Use when Codex needs to sharpen terminology, resolve ambiguous domain concepts, update CONTEXT.md, create ADRs, or support grill-with-docs, triage, TDD, diagnosis, or architecture work with durable domain language.
Clarify a feature, refactor, architecture idea, or product plan against existing code and domain docs. Use when requirements, terminology, constraints, or success signals are unclear before to-prd, to-issues, triage, or implementation, and Codex should update CONTEXT.md or ADRs only when domain terms or decisions crystallize.
Scan a codebase for architecture friction and deepening opportunities. Use when Codex needs to audit old code, find shallow modules, improve testability, identify seams before implementation, or report architecture blockers without directly changing product code.
Move issues, external PRs, new ideas, manual test feedback, existing-codebase audits, and regression reports through workflow triage states. Use when Codex needs to classify work, verify claims, detect already-implemented behavior, ask for missing info, create agent-ready briefs, or route changes before implementation.
Lightweight acceptance gate for completed slices, bug fixes, PRs, or implementation branches. Use when Codex needs to verify that work matches the originating issue or PRD, prove acceptance criteria and regression checks, decide pass/fail/blocked before handoff, or record acceptance evidence in GitHub, a PR, or local markdown.
| name | tdd |
| description | Test-driven development for one feature slice or bug fix. Use when Codex should work red-green-refactor, add behavior-focused tests, protect public interfaces, or turn a repro into a regression test during implementation. |
Use TDD to build one behavior at a time through public interfaces.
Read docs/agents/domain.md and docs/agents/verification.md if they exist.
Pick the highest useful public interface:
If no good seam exists, state the limitation and use the best command/manual verification available. Do not invent brittle tests just to appear test-first.
Write one focused test for one observable behavior. It should fail for the right reason when practical.
Implement the smallest change that passes the test. Avoid speculative interfaces or future options.
Clean duplication or awkward design only after the test is green. Keep the public behavior unchanged and rerun the focused check after each meaningful refactor.
Add the next behavior only after learning from the previous cycle. Stop when the work item's acceptance criteria are covered.
For handoff and acceptance, record:
