一键导入
clarification
Software factory clarification — use when gathering requirements before planning. Runs structured Q&A to produce a confirmed clarification summary.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Software factory clarification — use when gathering requirements before planning. Runs structured Q&A to produce a confirmed clarification summary.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 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.
| name | clarification |
| description | Software factory clarification — use when gathering requirements before planning. Runs structured Q&A to produce a confirmed clarification summary. |
| version | 0.1.0 |
Gather everything needed before any planning begins. One organized batch of questions — not a back-and-forth interrogation.
After getting answers, produce a structured summary:
## Clarification Summary
**Request:** <one-sentence restatement>
**Scope:** <what's in, what's out>
**Success criteria:** <observable outcomes>
**Tech stack:** <languages, frameworks, versions>
**Manual validation required:** <yes/no, what triggers it>
**Assumptions confirmed:** <list of things user explicitly confirmed>
**Out of scope confirmed:** <list of things user explicitly excluded>
Ask the user: "Does this summary accurately capture your request? Confirm to proceed to planning."
Do not proceed until user explicitly confirms. Write the confirmed summary to memory under key clarification_summary.