write-spec

The write-spec skill transforms vague feature ideas and problem statements into structured product requirements documents (PRDs) and feature specifications. It guides users through a conversational discovery process, asking targeted questions about user problems, success metrics, constraints, and prior work to gather the context needed for a complete specification. The skill handles the full spectrum of inputs, from one-line feature requests to complex enterprise requirements.

This skill generates comprehensive PRDs with clearly defined problem statements, measurable goals and non-goals, user stories organized by persona, prioritized requirements with acceptance criteria, and success metrics split into leading and lagging indicators. It can optionally pull context from connected project trackers, knowledge bases, and design tools to enrich the spec with existing research, related tickets, and design artifacts. The skill categorizes requirements by priority (Must-Have, Nice-to-Have, Future Considerations) and surfaces open questions tagged by responsible party.

Ideal for product managers scoping new features, engineering leads defining technical requirements, founders turning ideas into actionable plans, and teams needing to align stakeholders around a shared understanding of what will be built and why. The skill works iteratively, allowing users to refine sections, expand details, and generate follow-up artifacts like design briefs or engineering ticket breakdowns once the core spec is complete.