Menu
Software factory TDD implementation — use when implementing a phase. Enforces red-green discipline and code security standards before committing.
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.
Software factory clarification — use when gathering requirements before planning. Runs structured Q&A to produce a confirmed clarification summary.
Software factory memory protocol — use when reading or writing factory state. Covers JSONL memory operations, well-known keys, and agent startup protocol.
Software factory OpenTelemetry tracing — use when emitting traces for factory work. Covers root trace, phase sub-traces, and bi-directional linking.
Software factory spec and planning — use when producing a technical spec and phased implementation plan after clarification is confirmed.
Software factory validation gate — use when checking phase completion. Verifies automated tests pass and coordinates manual validation if required.
Software factory master workflow — use when starting or orchestrating a full factory run, coordinating clarification → spec → TDD implementation → validation phases.
Based on SOC occupation classification
| name | tdd-implementation |
| description | Software factory TDD implementation — use when implementing a phase. Enforces red-green discipline and code security standards before committing. |
| version | 0.1.0 |
For every unit of behavior:
Do not write implementation code before the failing test exists. Do not proceed past a failing test.
Read your phase spec from memory (implementation_plan, find the matching phase by name). Implement only what is in that phase. If you discover scope that should be in another phase, write a note to memory under scope_note:<phase_name> and stop — do not expand scope.
If a test fails unexpectedly (not the current TDD step), stop. Write to memory:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/memory.py" write \
--key "unexpected_failure:<phase_name>" \
--value '{"test":"<name>","error":"<message>","files_changed":["..."]}' \
--tags "failure,needs_attention"
Then surface the failure to the user. Do not continue with other tests.
Every change must be checked by the reviewer agent before committing. The reviewer checks for:
0.0.0.0 binding without intent)Do not commit a phase until the reviewer approves it.