specify
Create a product specification that defines what to build and why, without prescribing how.
Best use case
specify is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a product specification that defines what to build and why, without prescribing how.
Teams using specify should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/specify/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How specify Compares
| Feature / Agent | specify | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a product specification that defines what to build and why, without prescribing how.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Specify Skill Define features with clear product specifications. ## When to Activate This skill is relevant when: - Creating product specifications for new features - Defining what to build and why - Documenting user needs and acceptance criteria - Establishing clear scope boundaries ## Core Principles ### Focus on Value - Why are we building this? - What is the user benefit? - Clear problem statement - Measurable success metrics ### Clear Scope - Define what is in scope - Define what is out of scope - Prevent scope creep - MVP vs full feature clarity ### User-Centric - Write user stories focused on goals - Not system functions - Target user pain points - Desired outcomes over implementation ### Outcome-Oriented - Describe desired outcomes - Avoid implementation details - No technical prescriptions - Product thinking, not technical thinking ## Quick Checks When creating specifications, verify: - [ ] Clear problem statement exists - [ ] Goals are well-defined and measurable - [ ] User stories follow "As a [role], I want to [action] so that [benefit]" - [ ] Acceptance criteria are specific and testable - [ ] Functional requirements defined - [ ] UI/UX expectations documented - [ ] Performance expectations set - [ ] Edge cases identified (empty states, errors, boundaries) - [ ] Out of scope explicitly stated - [ ] Success metrics defined - [ ] No technical implementation details included - [ ] No API endpoint designs - [ ] No database schemas - [ ] No architecture decisions - [ ] No code structure or patterns
Related Skills
wireframe
Create markdown wireframes with detailed UX descriptions from a product specification. Senior UX Designer perspective inspired by Notion and Linear.
ux_redesign
Redesign a feature or page from a Principal UX Designer's perspective.
tech_review
Senior Principal Engineer performing thorough technical review of implementation plans before development.
tasks
Break down an approved implementation plan into specific, actionable tasks.
skeptical_review
Perform a critical, skeptical code review of the project from the perspective of a Principal Engineer.
security_agent
Perform a full security review of the codebase (Node.js & React focus).
review_plan
Review the technical implementation plan against the specification.
review_domain
Perform a thorough architectural review of a domain model.
review_constitution
Review and stress-test the technical constitution after /constitute.
retro
Reflect on the completed feature, document lessons learned, and improve workflows.
release_gate
Final Go/No-Go check and release preparation.
quality
Comprehensive quality assurance and functionality verification. Edge case testing and code quality audit.