write-spec

To generate a PRD from a vague feature idea, provide a problem statement or feature concept to the Skill. It then produces a complete PRD that defines problems, goals, and user stories.

A product specification includes sections for Problem Statement, Goals, Non-Goals, User Stories, Requirements, Open Questions, and a Timeline with phased milestones for structured product management.

To write user stories and acceptance criteria for a feature request, input the user request into the Skill. It guides teams through context gathering to produce structured user stories and clear acceptance criteria.

Yes, you can break a product feature into phases and milestones. The Skill supports phased planning by dividing work into distinct phases with milestones and acceptance criteria to aid prioritization.

To create a complete PRD, you need to provide information for context gathering, including the problem, target users, success metrics, and constraints to shape the specification.

To define non-goals and scope for a product feature, the Skill guides teams through trade-offs and context gathering to explicitly list non-goals and align on the feature scope.