write-spec Skill
Write a feature spec or PRD from a problem statement or feature idea. 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. Published by anthropics in knowledge-work-plugins.
Decision snapshot
Is this a fit?
Data analysis, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
23 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is write-spec Skill?
Write a feature spec or PRD from a problem statement or feature idea. 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. Published by anthropics in knowledge-work-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Writing
- Data analysis use cases
- Writing use cases
Declared skill metadata
- Source file: product-management/skills/write-spec/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use write-spec Skill
- Use it for data analysis.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/knowledge-work-plugins
- Skill file: product-management/skills/write-spec/SKILL.md
What it does
Write a feature spec or PRD from a problem statement or feature idea. 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.
Skill instructions
Write Spec If you see unfamiliar placeholders or need to check which tools are connected, see 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 befo
Verified compatibility and discovery
Frequently asked questions
What is write-spec?
write-spec is a open-source AI agent skill with Copy skill directory. Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success.
Who is write-spec best for?
write-spec is best for reusing agent instructions, scripts, and references, data analysis workflows, writing workflows.
How do I install write-spec?
Install or run write-spec using Copy skill directory. Check write-spec for the latest setup command.
Is write-spec actively maintained?
write-spec may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
