write-spec
Writes a feature spec or PRD from a problem statement: goals and non-goals, success metrics, acceptance criteria and phases.
- Kind
- Skill
- Works with
- Claude Code
- Source
- Claude knowledge-work plugins @ 2574e29377c7
- Path
- product-management/skills/write-spec/SKILL.md
- License
- Apache-2.0
- Jobs
- Planning, Documentation
InstallInstall it from a plugin marketplace.
claude plugin install product-management@knowledge-work-plugins
# Write Spec
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
Write a feature specification or product requirements document (PRD).
## Usage
```
/write-spec $ARGUMENTS
```
## Workflow
### 1. Understand the Feature
Ask the user what they want to spec. Accept any of:
- A feature name ("SSO support")
- A problem statement ("Enterprise customers keep asking for centralized auth")
- A user request ("Users want to export their data as CSV")
- A vague idea ("We should do something about onboarding drop-off")
### 2. Gather Context
Ask the user for the following. Be conversational — do not dump all questions at once. Ask the most important ones first and fill in gaps as you go:
- **User problem**: What problem does this solve? Who experiences it?
- **Target users**: Which user segment(s) does this serve?
- **Success metrics**: How will we know this worked?
- **Constraints**: Technical constraints, timeline, regulatory requirements, dependencies
- **Prior art**: Has this been attempted before? Are there existing solutions?
### 3. Pull Context from Connected Tools
If **~~project tracker** is connected:
…