Menu
Produce a clear, review-ready SDD specification skeleton in Markdown.
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.
Based on SOC occupation classification
Safely sync a branch with origin/main using fetch + rebase, with an optional "accept current" conflict policy.
Improve acceptance criteria so they are testable, unambiguous, and complete.
Add an MCP integration section (tools, auth, error handling, observability, tests) to an existing spec.
Extract MUST/SHOULD/MAY requirements, constraints, flows, and open questions from long epic/PRD text (PDF/TXT export).
Identify edge cases, security/privacy issues, operational risks, and delivery risks in a spec.
Propose a safe rollout/migration plan with monitoring and rollback steps.
| name | sdd-spec-template |
| description | Produce a clear, review-ready SDD specification skeleton in Markdown. |
Produce a clear, review-ready SDD specification in Markdown.
Write an SDD specification in Markdown using this exact structure:
1. Title & context
2. Goal (1–3 sentences)
3. Non-goals (bullets)
4. Scope / Impact (what changes where; API/DB/UI; compatibility)
5. Assumptions (if any)
6. User stories / Scenarios (brief)
7. Acceptance criteria (AC) – 5–12 verifiable items
8. Edge cases & error handling
9. Security & privacy (if relevant)
10. Telemetry/Logging (if relevant)
11. Test plan (unit/integration/e2e; mocks; minimum set)
12. Rollout / Migration (if relevant)
13. Open questions
Constraints:
- Keep it concise, but specific.
- AC must be testable and unambiguous.
- If information is missing, ask up to 3 targeted questions, otherwise proceed with clearly stated assumptions.