spec-create
A 5-step, file-based workflow for creating consistent technical specifications through interactive collaboration.
Install
mkdir -p .claude/skills/spec-create && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10516" && unzip -o skill.zip -d .claude/skills/spec-create && rm skill.zipInstalls to .claude/skills/spec-create
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create technical specifications through collaborative 5-step workflowKey capabilities
- →Discover requirements
- →Scope specifications
- →Build content
- →Cross-reference
- →Polish document
How it works
It guides users through a 5-step collaborative workflow using a micro-file architecture for lean specification creation.
Inputs & outputs
When to use spec-create
- →Defining new feature requirements
- →Documenting system architectures
- →Planning complex development projects
About this skill
Create Specification Workflow
Goal
Create a complete, consistent technical specification through structured collaboration with the user.
Role
You are a specification facilitator collaborating with a domain expert peer. You guide the process and structure; the user provides the domain knowledge and decisions.
Workflow Architecture
This workflow uses a micro-file architecture with the following design principles:
Micro-File Design
Each step is a self-contained markdown file in ./references/. Files are small, focused, and independently loadable. This keeps context windows lean and instructions precise.
Just-In-Time Loading
Step files are loaded only when needed — never preloaded. When a step completes and the user chooses to continue, load the next step file at that point.
Sequential Enforcement
Steps must be completed in order: discover → scope → build → crossref → polish. Never skip steps. Never go backwards unless explicitly restarting.
State Tracking
The spec document's frontmatter stepsCompleted array tracks which steps have been finished. This enables continuation of interrupted workflows.
Step Processing Rules
When processing any step file:
- Read the entire step file before taking any action.
- Follow the step's MANDATORY EXECUTION RULES exactly as written.
- Do not combine steps — complete one fully before loading the next.
- Present menus exactly as specified in the step file.
- Wait for user input at every decision point — never assume choices.
- Update the spec document after each step completes (write stepsCompleted).
Critical Rules
- Never invent content — all domain content comes from the user or referenced documents.
- Never skip user confirmation — every draft must be reviewed before being written.
- Never load multiple step files — one step at a time, loaded just-in-time.
- Never prescribe section structure — the user decides what sections their spec needs.
- Always write progress — update the document's frontmatter after each step.
Initialization Sequence
- Load config if available at
.claude-plugin/config.json. - Route to
./references/step-01-discover.mdto begin.
When not to use it
- →Skipping steps in the workflow
Limitations
- →Steps must be completed in order
How it compares
It enforces a strict, sequential process rather than allowing unstructured document creation.
Compared to similar skills
spec-create side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| spec-create (this skill) | 0 | 4mo | No flags | Intermediate |
| project-planner | 32 | 9mo | Review | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
| planning-agent | 5 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context
pdd
mikeyobrien
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
trellis-brainstorm
mindfold-ai
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.