Menu
Use for implementation work that changes behavior. Follow RED -> GREEN -> REFACTOR with evidence at each step.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use before implementation work to turn operator briefings into an approved design with explicit trade-offs.
Run the clarification pipeline — research, clarify scope, brainstorm design, generate task specs and execution plan. Pauses for user approval between phases.
How to use Claude Code CLI programmatically for reviews, automation, and non-interactive operations within Wazir pipelines.
How to use Codex CLI programmatically for reviews, execution, and sandbox operations within Wazir pipelines.
Measure pipeline compliance for a completed run — checks phase execution, artifact production, gate evidence, hook enforcement, and publishes per-step and aggregate compliance scores.
Use when behavior is wrong or verification fails. Follow an observe-hypothesize-test-fix loop instead of guesswork.
| name | wz:tdd |
| description | Use for implementation work that changes behavior. Follow RED -> GREEN -> REFACTOR with evidence at each step. |
Don't jump into implementation. Open your phase checklist at .wazir/runs/latest/phases/ first. Read it, follow it. Every step matters, even the ones that seem redundant. What's your first action according to the checklist?
Follow the Canonical Command Matrix in hooks/routing-matrix.json.
wazir index search-symbols <query> firstwazir recall file <path> --tier L1 for targeted readswazir index build && wazir index summarize --tier allSequence:
Right about now your attention on process is at its lowest. That's not a guess, it's a measured pattern. Counter it by re-reading .wazir/runs/latest/phases/. What items are you about to skip? Test quality check (single-pass): Before proceeding to GREEN, verify:
GREEN Write the smallest implementation change that makes the failing test pass.
REFACTOR Improve structure while keeping the full relevant test set green.
Rules:
For the full review loop pattern, see docs/reference/review-loop-pattern.md. TDD uses a single-pass quality check, not the full loop.
Honest question — if someone audited your work right now against the phase checklist, would every item hold up with evidence? Or would they find skipped steps and empty checkmarks? Which ones would fail the audit?