What problem does it solve? Turning a vague feature idea into a complete product spec or PRD is hard: key context like audience, success criteria, and scope boundaries often goes undocumented, leaving engineers and stakeholders misaligned. This Skill guides an interactive elicitation process and produces a structured spec file covering the problem, audience, requirements, and tradeoffs. ## Core Features & Use Cases - Interactive Elicitation: Asks targeted questions about the problem, audience, benefits, success and failure indicators, and explicit non-goals before drafting anything. - Structured Spec Template: Drafts the document using a defined template with sections for Background, Hypothesis, Success Criteria, Requirements, Non-requirements, and Tradeoffs. - Iterative Refinement and Saving: Revises the draft based on feedback and saves the final result as a dated markdown file like spec-<feature-name>-MM-DD-YYYY.md. - Use Case: A product manager asks to spec a new notifications feature; the Skill interviews them about users and success metrics, drafts a full PRD, iterates on feedback, and saves the final document. ## Quick Start Ask the assistant to write a product spec for your new feature idea and answer its questions about the problem, audience, and success criteria.
