Menu
Software factory spec and planning — use when producing a technical spec and phased implementation plan after clarification is confirmed.
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 TDD implementation — use when implementing a phase. Enforces red-green discipline and code security standards before committing.
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 | spec-planning |
| description | Software factory spec and planning — use when producing a technical spec and phased implementation plan after clarification is confirmed. |
| version | 0.1.0 |
Read clarification_summary from memory. Do not begin without it.
Produce a document with these sections:
Ordered list of phases. Each phase:
name: kebab-case identifierdescription: what it buildstests_first: what failing tests to write (specific function/class names)files: exact files to create or modifyparallel: true if this phase can run concurrently with another (name which)manual_validation: true/false and trigger reason if truecommit_message: the git commit message for when this phase is completePresent both documents. Incorporate feedback. Do not write to memory until user explicitly confirms.
Write to memory:
spec_document — the full specimplementation_plan — the confirmed plan as a JSON array of phase objects