Write Spec

Write a feature spec or PRD from a problem statement or feature idea. Turns vague ideas into structured documents with goals, non-goals, success metrics, user stories, and acceptance criteria.

The Write Spec skill structures messy feature ideas into clear, actionable PRDs. It forces the right questions — who's the user, what's the job-to-be-done, how do we measure success — and produces a document engineers can build from and stakeholders can review.

When to use

Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

Examples

Feature spec from a Slack message

Turn a vague request into a structured PRD

Write a spec for this: 'We need users to be able to invite their team.' It's for a SaaS project tool with 3 user roles.

Phase a large feature

Break a big feature into phased delivery

Write a phased spec for adding real-time collaboration to our document editor. Phase 1 should ship in 6 weeks.

Define success metrics

Add measurable outcomes to a spec

I have a spec for our new onboarding flow but it's missing success metrics. Help me define what good looks like.