specify
Skill0 starsChanged 36 days agoMITView on GitHub
Specification-driven development skill. Guides users through Jobs-to-Be-Done (JTBD) decomposition to generate comprehensive specs. Use when user wants to create specifications, define features, plan a new project, or says /specify.
- Deletes or force-pushes
29 other projects use a version of this.
Adopted by
Most recently taken up by
- ZaxbyHub/opencode-swarmtheir own version, first seen Nov 15, 2026
- danielcherubini/skillstheir own version, first seen Nov 11, 2026
- joeldevz/skynex-pitheir own version, first seen Nov 8, 2026
- Buddhilive/buddhi-clitheir own version, first seen Nov 1, 2026
- jantichy/claudetheir own version, first seen Oct 27, 2026
- totalfrank/skillstheir own version, first seen Oct 27, 2026
Used with
Projects with it also use discovery, discover and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
robzolkosSkilldiscovery
Quick user-centric interview to capture requirements from a time-poor stakeholder.
Also in 3 projects that use this
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 4 projects that use this
MicrosoftSkillspec-review
Independent, multi-model review of a design or spec **before** any code is written, for the microsoft/winappcli repo. Activate when a contributor asks to "review this spec", "review my design", "review this design doc", "validate this approach", "should we build this", "spec review", "design review", or "feature review". Fans out parallel sub-agents — each doing its OWN research against the real codebase and ecosystem rather than trusting the spec — covering necessity & scope, approach & alternatives, feasibility vs reality, risks & unknowns, DX & user impact, and a different-model-family cross-check. Emits a decision-oriented recommendation (proceed / proceed-with-changes / reconsider) to stdout. This is the PRE-CODE companion to the pr-review skill (which reviews code already written); use spec-review at the design/spec stage, not on an implemented diff. Does NOT write code or edit the spec.
Also in 3 projects that use this
MicrosoftSkillinit
Also in 5 projects that use this
MetaSkillroadmap
Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.
Also in 3 projects that use this
sahinSkillexecute
Also in 3 projects that use this
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- ZaxbyHub/opencode-swarm★ 531same name
- zaxbysauce/opencode-swarm★ 519same name
- genkovich/sdd★ 187same name
- team-attention/hoyeon★ 173same name
- ArvorCo/Relentless★ 98same name
- jantichy/claude★ 52same name
- mehrad-dm/mastermind★ 23same name
- agent-ix/quoin★ 20same name
- danielcherubini/skills★ 14same name
- stormlightlabs/thunderus★ 4same name
19 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- north-starSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
32 rules. 0 are common, 23 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
23
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
No clutter in the project directory
- Distinctive: line 85
Auto-cleanup: After successful spec generation (Phase 4-5 complete), delete the state file automatically.
- Very specific: line 92
Check for existing specs/ directory
- Distinctive: line 94
If specs exist, offer to extend or start fresh
- Distinctive: line 97
Ask: "What job are your users trying to accomplish?"
- Distinctive: line 107
No semantic overlap between topics
- Distinctive: line 113
Ask clarifying questions about ambiguous areas
- Distinctive: line 141
Use Context7 for library documentation
- Distinctive: line 150
Update state with per-topic research:
- Very specific: line 173
When significant design decisions exist, generate motif.md exploration document.
- Very specific: line 185
Create motif.md in project root
- Distinctive: line 187
Ask user to review and choose
- Distinctive: line 200
Update
CLAUDE.md: - Add Specifications section if missing - Distinctive: line 216
If CLAUDE.md exists but lacks a Specifications section, inject:
- Distinctive: line 231
Check if CLAUDE.md exists
- Very specific: line 232
Check if ## Specifications section exists
- Distinctive: line 233
If missing, insert after first heading or at document start
- Very specific: line 378
When $ARGUMENTS is init:
- Very specific: line 380
Create specs/ directory if not exists
- Very specific: line 381
Create specs/README.md with basic structure
- Distinctive: line 382
Update CLAUDE.md with Specifications section
- Distinctive: line 383
Do NOT run full workflow
- Distinctive: line 391
Do NOT proceed to research or generation
- Very specific: line 395
When $ARGUMENTS starts with research:
- Distinctive: line 399
Update state with research results
- Distinctive: line 400
Do NOT generate specs
- Distinctive: line 408
Run Phase 4 and 5 only
- Distinctive: line 410
Delete state file after successful generation
- Distinctive: line 414
MANDATORY: Before generating specs, read the template files:
- Distinctive: line 419
Follow these templates exactly for consistent output.
- Distinctive: line 423
After running /specify, verify success by checking:
- Very specific: line 426
README links work: All links in specs/README.md resolve
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Specification Generator
Transform Jobs to Be Done (JTBD) into structured specification documents.
Sub-commands
Parse $ARGUMENTS to determine which sub-command to run:
| Command | Description |
| (empty) | Full interactive workflow |
init | Initialize specs/ structure only |
decompose | JTBD decomposition only |
research <topic> | Research specific topic |
generate | Generate specs from existing decomposition |
When to Use Each Sub-command
Starting Fresh?
→ Use /specify (full workflow)
Already Have specs/ Directory?
→ Use /specify init (structure only)
Just Need to Break Down a Feature?
→ Use /specify decompose
Need to Research a Specific Area?
→ Use /specify research <topic>
Have Decomposition, Ready to Write Specs?
→ Use /specify generate
Dependencies
This skill works best when the following are available:
- Context7 MCP - For external library documentation research
- Task tool with Explore agent - For codebase pattern discovery
- Write/Edit tools - For generating spec files
State Management
Track workflow state in a cache directory to avoid polluting the project:
State file location: ~/.cache/claude/specify/{project-hash}.json
The {project-hash} is derived from the absolute path of the project directory (e.g., MD5 or similar hash). This allows:
- Multiple projects to have independent state
- No clutter in the project directory
- Easy cleanup with
rm -rf ~/.cache/claude/specify/
To compute the state file path:
# Get project hash from current working directory
project_hash=$(echo -n "$(pwd)" | md5 | cut -c1-16)
state_file="$HOME/.cache/claude/specify/${project_hash}.json"State structure:
{
"projectPath": "/absolute/path/to/project",
"jtbd": "string - the job to be done statement",
"topics": [
{
"id": "topic-slug",
"name": "Topic Name",
"description": "One sentence description",
"status": "pending|researched|specified",
"designDecisions": []
}
],
"phase": "decompose|research|design|generate",
"projectType": "detected project type"
}Auto-cleanup: After successful spec generation (Phase 4-5 complete), delete the state file automatically. State is only needed for resuming incomplete workflows.
Phase 1: JTBD Decomposition
Workflow
- Detect project context
- Check for existing
specs/directory - Detect project type from package.json, Cargo.toml, go.mod, etc.
- If specs exist, offer to extend or start fresh
- Check for existing
- Capture JTBD
- Ask: "What job are your users trying to accomplish?"
- Focus on outcome, not solution
- Example: "Users need to track personal finances to understand spending"
- Decompose into topics
- Break JTBD into 3-7 distinct topics
- Each topic must pass the "One Sentence Without 'And'" test
- Topics should be 5-15 words describing a single concern
- Validate topics
- No semantic overlap between topics
- Each topic is actionable (uses verbs like: track, display, manage, validate, sync)
- Topics are bounded and testable
- Present for refinement
- Show topics in a table with status
- Ask clarifying questions about ambiguous areas
- Allow user to accept, modify, split, or merge topics
Example Decomposition
JTBD: "Users need to track personal finances to understand spending"
Topics:
1. transaction-tracking - Recording income and expense transactions
2. category-management - Organizing transactions into categories
3. budget-system - Setting and tracking spending limits
4. reporting-analytics - Generating insights and visualizations
5. data-import - Importing data from bank statementsPhase 2: Research
For each topic, spawn an Explore subagent to gather:
- Codebase patterns
- Existing similar features
- Relevant types, traits, modules
- Architectural patterns in use
- External research
- Best practices for the domain
- API patterns if applicable
- Use Context7 for library documentation
- Design decisions
- Identify architectural choices needed
- Prepare options with trade-offs
- Flag decisions requiring user input
Research Output
Update state with per-topic research:
{
"id": "topic-slug",
"research": {
"existingPatterns": ["pattern descriptions"],
"externalReferences": ["urls or summaries"],
"designDecisions": [
{
"question": "How should X be implemented?",
"options": ["Option A", "Option B"],
"tradeoffs": "A is simpler, B is more flexible"
}
],
"dependencies": ["other-topic-id"],
"complexity": "low|medium|high"
}
}Phase 3: Design Decisions (motif.md)
When significant design decisions exist, generate motif.md exploration document.
See motif.md for the template.
When to Generate motif.md
- Multiple valid architectural approaches exist
- User preferences matter for the outcome
- Trade-offs are significant and not obvious
Workflow
- Create
motif.mdin project root - Present options with pros/cons and references
- Ask user to review and choose
- Record decisions in state
Phase 4: Spec Generation
Generate specification files using templates.
See spec.md for the full template.
Files to Create
specs/README.md- Index of all specificationsspecs/{topic}.md- One file per topic- Update
CLAUDE.md- Add Specifications section if missing
Spec File Sections
Each spec should include (as applicable):
- Overview (purpose, goals, non-goals)
- Architecture (component structure, diagrams)
- Core Types (with field tables)
- API / Behaviors
- Database Schema (if applicable)
- Configuration
- Security Considerations
- Implementation Phases
Phase 5: CLAUDE.md Update
If CLAUDE.md exists but lacks a Specifications section, inject:
## Specifications
**IMPORTANT:** Before implementing any feature, consult `specs/README.md`.
- **Assume NOT implemented.** Specs describe intent; code describes reality.
- **Check the codebase first.** Search actual code before concluding.
- **Use specs as guidance.** Follow design patterns in relevant spec.
- **Spec index:** `specs/README.md` lists all specs by category.Merge Logic
- Check if
CLAUDE.mdexists - Check if
## Specificationssection exists - If missing, insert after first heading or at document start
- Preserve all existing content
User Interaction Pattern
Full Workflow Example
User: /specify
Claude: I'll help create specifications for your project.
**Project Detection:**
- Type: TypeScript/Node.js
- Existing specs: No
**Step 1: Define Your Job to Be Done**
What problem are you solving for your users? (Focus on outcome, not solution)
---
User: Users need to manage their reading list and track books they've read
Claude: **Topics Identified:**
| # | Topic | Description | Status |
|---|-------|-------------|--------|
| 1 | book-catalog | Storing and retrieving book information | Ready |
| 2 | reading-status | Tracking read/unread/in-progress state | Ready |
| 3 | list-management | Creating and organizing reading lists | Ready |
| 4 | reading-progress | Recording pages read and notes | Ready |
**Questions:**
1. Should users be able to share lists with others?
2. Do you need integration with book databases (OpenLibrary, Google Books)?
---
User: Yes to sharing, no external integrations for now
Claude: [Updates topics, spawns research subagents]
**Research Complete. Design Decision Required:**
Created `motif.md` for sharing architecture. Please review and let me know which approach you prefer.
---
User: I like Option B - simple link sharing
Claude: Generating specifications...
**Created:**
- specs/README.md
- specs/book-catalog.md
- specs/reading-status.md
- specs/list-management.md
- specs/reading-progress.md
- specs/sharing.md
- Updated CLAUDE.md
Ready for implementation planning.Example Output
Generated specs/README.md
# Reading Tracker Specifications
Design documentation for a personal reading list management application.
## Overview
This directory contains specifications for the project's features and systems.
**Status Legend:**
- **Planned** - Design complete, not yet implemented
- **In Progress** - Currently being implemented
- **Implemented** - Feature complete and in production
---
## Core Features
| Spec | Status | Purpose |
|------|--------|---------|
| [book-catalog.md](./book-catalog.md) | Planned | Storing and retrieving book information |
| [reading-status.md](./reading-status.md) | Planned | Tracking read/unread/in-progress state |
| [list-management.md](./list-management.md) | Planned | Creating and organizing reading lists |
| [reading-progress.md](./reading-progress.md) | Planned | Recording pages read and notes |
## Social Features
| Spec | Status | Purpose |
|------|--------|---------|
| [sharing.md](./sharing.md) | Planned | Link-based list sharing with others |Generated specs/book-catalog.md (excerpt)
# Book Catalog Specification
**Status:** Planned
**Version:** 1.0
**Last Updated:** 2025-01-15
---
## 1. Overview
### Purpose
The book catalog provides the core data model for storing and retrieving book information. It serves as the foundation for all other features in the reading tracker.
### Goals
- **Complete book metadata** - Store title, author, ISBN, cover image, and page count
- **Fast lookup** - Support search by title, author, or ISBN
- **Extensible schema** - Allow custom fields for user-defined metadata
### Non-Goals
- **External sync** - No integration with Goodreads or other services (deferred)
- **Social features** - Book recommendations handled in separate spec
---
## 2. Architecture
### Component Structure
src/
├── models/
│ └── book.ts # Book entity and types
├── repositories/
│ └── book-repo.ts # Data access layer
└── services/
└── book-service.ts # Business logicInit Sub-command
When $ARGUMENTS is init:
- Create
specs/directory if not exists - Create
specs/README.mdwith basic structure - Update
CLAUDE.mdwith Specifications section - Do NOT run full workflow
Decompose Sub-command
When $ARGUMENTS is decompose:
- Run Phase 1 only
- Save state to cache file (see State Management)
- Do NOT proceed to research or generation
Research Sub-command
When $ARGUMENTS starts with research:
- Load state from cache file (see State Management)
- Research the specified topic (or all if none specified)
- Update state with research results
- Do NOT generate specs
Generate Sub-command
When $ARGUMENTS is generate:
- Load state from cache file (see State Management)
- Require completed decomposition
- Run Phase 4 and 5 only
- Generate all spec files
- Delete state file after successful generation
Template Usage
MANDATORY: Before generating specs, read the template files:
motif.md- For design exploration documentsspec.md- For specification filesreadme.md- For the specs index
Follow these templates exactly for consistent output.
Verification
After running /specify, verify success by checking:
- Spec files exist:
ls specs/*.md - README links work: All links in
specs/README.mdresolve - CLAUDE.md updated: Specifications section present
- State auto-cleaned: Cache file deleted after successful generation
Quick Reference
| Phase | Output | Key Files |
| Decompose | Topics list | ~/.cache/claude/specify/{hash}.json |
| Research | Design decisions | cache state updated |
| Design | Architecture choices | motif.md (if needed) |
| Generate | Specifications | specs/*.md, specs/README.md |
| Finalize | CLAUDE.md update, state cleanup | CLAUDE.md |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

