Product Spec Kit
Generates a comprehensive product specification kit, streamlining requirements gathering and ensuring consistent documentation for successful projects.
Install on your platform
We auto-selected Claude Code based on this skillβs supported platforms.
Run in terminal (recommended)
claude mcp add product-spec-kit npx -- -y @trustedskills/product-spec-kit
Or manually add to ~/.claude/settings.json
{
"mcpServers": {
"product-spec-kit": {
"command": "npx",
"args": [
"-y",
"@trustedskills/product-spec-kit"
]
}
}
}Requires Claude Code (claude CLI). Run claude --version to verify your install.
About This Skill
What it does
The Product Spec Kit skill assists Product Managers in generating structured, high-quality documentation for product development. It supports both comprehensive workflows (Product Requirements Document [PRD] β Plan β User Stories) and standalone document creation like individual stories or bug reports. The tool ensures consistency by adhering to a defined constitution and mirroring the userβs language in generated documents.
When to use it
- Creating a Product Requirements Document (PRD).
- Generating an epic and associated user stories/tasks.
- Clarifying existing product specifications like PRDs, Release Plans, User Stories, Tasks or Bugs.
- Producing standalone documentation for individual items such as a PRD, Plan, Story, Task, or Bug.
Key capabilities
- Generates Product Requirements Documents (PRDs).
- Creates epics and associated user stories/tasks.
- Supports clarification of existing product specifications.
- Adheres to a defined constitution for consistent documentation principles.
- Uses the language specified by the user in generated documents.
Example prompts
- "Create a PRD for our new mobile app feature."
- "Can you help me break down this PRD into smaller stories and tasks?"
- βI need to clarify some acceptance criteria for an existing User Story.β
Tips & gotchas
- The skill operates according to a constitution (rules/product-speckit-constitution.md) that dictates principles like clear requirements, design-driven acceptance criteria, and functional descriptions over visual details. These principles are non-negotiable.
- If you don't specify the type of specification you want to create initially, the skill will ask for clarification.
- To break down a PRD into smaller parts (Epics/Stories), you must first either validate an existing PRD or create one.
Tags
TrustedSkills Verification
Unlike other registries that point to live repositories, TrustedSkills pins every skill to a verified commit hash. This protects you from malicious updates β what you install today is exactly what was reviewed and verified.
Security Audits
| Gen Agent Trust Hub | Pass |
| Socket | Pass |
| Snyk | Pass |
π Community
Passed automated security scans.