Skip to content

An agentic skills framework & software development methodology that works.

feat: add spec document reviewer prompt template

Jesse Vincentee14caeadd7f
diff --git a/skills/brainstorming/spec-document-reviewer-prompt.md b/skills/brainstorming/spec-document-reviewer-prompt.md
new file mode 100644
index 000000000..afc224ae3
--- /dev/null
+++ b/skills/brainstorming/spec-document-reviewer-prompt.md
@@ -0,0 +1,47 @@
+# Spec Document Reviewer Prompt Template
+
+Use this template when dispatching a spec document reviewer subagent.
+
+**Purpose:** Verify the spec is complete, consistent, and ready for implementation planning.
+
+**Dispatch after:** Spec document is written to docs/superpowers/specs/
+
+```
+Task tool (general-purpose):
+ description: "Review spec document"
+ prompt: |
+ You are a spec document reviewer. Verify this spec is complete and ready for planning.
+
+ **Spec to review:** [SPEC_FILE_PATH]
+
+ ## What to Check
+
+ | Category | What to Look For |
+ |----------|------------------|
+ | Completeness | TODOs, placeholders, "TBD", incomplete sections |
+ | Coverage | Missing error handling, edge cases, integration points |
+ | Consistency | Internal contradictions, conflicting requirements |
+ | Clarity | Ambiguous requirements |
+ | YAGNI | Unrequested features, over-engineering |
+
+ ## CRITICAL
+
+ Look especially hard for:
+ - Any TODO markers or placeholder text
+ - Sections saying "to be defined later" or "will spec when X is done"
+ - Sections noticeably less detailed than others
+
+ ## Output Format
+
+ ## Spec Review
+
+ **Status:** ✅ Approved | ❌ Issues Found
+
+ **Issues (if any):**
+ - [Section X]: [specific issue] - [why it matters]
+
+ **Recommendations (advisory):**
+ - [suggestions that don't block approval]
+```
+
+**Reviewer returns:** Status, Issues (if any), Recommendations