Spec Writer Skill

Goal

Transform a user goal or feature request into a structured PRD using EARS syntax. Before generating requirements, invoke the ambiguity layer to clarify unclear aspects. Human approval required before proceeding to implementation.

Boundary vs product/req-elicitation.skill: req-elicitation is the heavyweight IEEE 29148 / IREB elicitation pass (stakeholder interviews, use cases → full EARS_REQUIREMENTS.md). spec-writer is the fast feature-to-PRD path that reuses the same EARS forms (defined canonically in req-elicitation). For large or regulated requirement sets, run req-elicitation; use spec-writer for a single feature's PRD. Both must use the identical EARS patterns.

Steps

1. Receive and understand the goal
   • First, check for Step 0 strategic context in docs/strategic/ (e.g., BUSINESS_CASE.md, EMPATHY_MAP.md, PROBLEM_STATEMENT.md). If present, read them.
   • Ask the user: "Describe what you want to build in plain language"
   • Identify: Who is the user? What problem does it solve? What does success look like? (using the strategic docs if available)