## Product Spec

From research to clear requirements in minutes

### Product Manager

Turns research briefs, user insights, and problem descriptions into structured product specs — covering what to build, why, who it's for, and how to measure success. Optimized for agent consumption so downstream skills can execute with clarity.

### How it works

1. **Feed it your inputs**  
   Share a research brief, customer feedback themes, support insights, or a problem statement. The agent gathers all available context from your project.

2. **Clarify and scope**  
   The agent identifies gaps, resolves ambiguity, and confirms scope boundaries before writing — so the spec is tight and actionable.

3. **Get a structured spec**  
   Receive a product spec with use cases, requirements, success criteria, and scope — ready to hand off to design spec and prototyping.

### Why use Product Spec

#### Research to requirements
Automatically synthesizes research briefs and user insights into structured, actionable requirements.

#### Agent-optimized output
Specs are structured for downstream agent consumption — design specs and prototypes execute better with clear inputs.

#### Built-in success criteria
Every spec includes measurable criteria you can review designs against, closing the loop from requirements to evaluation.

#### No enterprise overhead
Focused on what matters — problem, users, requirements, success criteria. No signoff sections, approval workflows, or stakeholder matrices.

### When to use Product Spec

#### Post-research scoping
You have a research brief and need to turn the top recommendation into a buildable spec.

#### Customer feedback synthesis
You have themes from customer calls or support channels and need to define what to build.

#### Ticket expansion
You have a brief ticket description that needs to be expanded into full requirements before design.

### More from your Product Manager

#### See Product Spec in action
See how Product Spec turns research and insights into structured requirements in minutes.