specification-writing
Write feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.
Best use case
specification-writing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Write feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.
Teams using specification-writing 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/specification-writing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How specification-writing Compares
| Feature / Agent | specification-writing | 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?
Write feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.
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.
Related Guides
SKILL.md Source
# Specification Writing ## Overview Write comprehensive feature specifications from business-level descriptions. Produces requirements, user stories, acceptance criteria, and scope boundaries that define WHAT to build without prescribing HOW. ## When to Use - Defining a new feature before planning or implementation - Formalizing vague feature requests into structured requirements - Clarifying scope boundaries for a feature area - Establishing acceptance criteria for user stories ## Key Principle Specifications describe desired behavior from the user's perspective. They define **what** the system should do, not **how** it should be built. Business value must be explicit in every requirement. ## Process 1. **Elicit requirements** - Extract functional and non-functional requirements from feature description 2. **Write user stories** - Author stories in standard format with personas 3. **Define acceptance criteria** - Testable conditions for each story (Given/When/Then) 4. **Identify edge cases** - Error scenarios and boundary conditions 5. **Clarify gaps** - Surface and resolve ambiguities and contradictions 6. **Document assumptions** - Make implicit assumptions explicit 7. **Define scope** - Clearly delineate in-scope vs. out-of-scope 8. **Human review** - Approve specification before planning ## Tool Use Invoke via babysitter process: `methodologies/spec-kit/spec-kit-specification` Full pipeline: `methodologies/spec-kit/spec-kit-orchestrator`
Related Skills
tech-writing-lint
Automated technical writing style and quality enforcement. Lint documentation with Vale, check for inclusive language, enforce style guides, and analyze readability metrics.
tech-writing-linter
Lint technical documentation for style, consistency, and readability
academic-writing-publication
Prepare manuscripts following APA, ASA, or discipline-specific guidelines with proper reporting standards and peer review navigation
philosophical-writing-argumentation
Compose clear, rigorous philosophical prose with well-structured arguments, anticipation of objections, and proper scholarly engagement with existing literature
grant-narrative-writing
Compose compelling research narratives for NEH, ACLS, and foundation funding proposals with clear significance statements
learning-objectives-writing
Write measurable, SMART learning objectives using Bloom's Taxonomy cognitive levels aligned with desired outcomes and assessment strategies
interpretive-writing
Create accessible interpretive content for diverse audiences including labels, wall text, catalog essays, educational materials, and digital content
grant-proposal-writing
Develop compelling funding proposals for foundations, government agencies, and corporations including narrative development, budget creation, and compliance documentation
style-specification
Create ultra-detailed musical style specifications including genres, BPM, instrumentation, vocal direction, production aesthetics, and reference tracks for AI music generation
lyric-writing
Write complete song lyrics with structural annotations and production notes optimized for AI music generation platforms like Suno and Udio
treatment-writing
Develop narrative synopses that tell the complete story cinematically, serving as sales documents and production blueprints
scene-writing
Write individual screenplay scenes with proper industry formatting, visual action, and dramatic structure