spec-writing

name	spec-writing
description	Creates clear, testable specifications from feature descriptions with user stories. Use when starting a new feature and needing a spec before planning.
alwaysApply	false
category	specification
tags	["speckit","specification","requirements","user-stories","acceptance-criteria"]
dependencies	["superpowers:brainstorming"]
tools	[]
usage_patterns	["feature-specification","requirements-documentation","user-story-creation"]
complexity	intermediate
model_hint	standard
estimated_tokens	1200
progressive_loading	true
modules	["modules/success-criteria-patterns.md","modules/specification-structure.md","modules/checklist-dimensions.md"]

Spec Writing

Overview

Create clear, complete, and testable specifications from natural language feature descriptions. Specifications focus on user value and business needs, avoiding implementation details.

When To Use

• Creating new feature specifications
• Refining existing specifications
• Writing user stories and acceptance criteria
• Defining success criteria

When NOT To Use

• Generating implementation tasks - use task-planning

Core Principles

Focus on user value and business needs rather than implementation details. Avoid specifying technology choices in requirement definitions unless strictly necessary. Ensure every requirement is testable and verifiable with measurable criteria. Limit clarification markers; make informed assumptions based on industry standards and document them explicitly.

Specification Structure

Mandatory Sections

1. Overview/Context: What problem does this solve?
2. User Scenarios: Who uses it and how?
3. Functional Requirements: What must it do?
4. Success Criteria: How do we know it works?

Optional Sections

• Success Criteria (when performance/security critical)
• Edge Cases (when special handling needed)
• Dependencies (when external systems involved)
• Assumptions (when decisions made with incomplete info)

See: modules/specification-structure.md for detailed templates and guidelines

Quality Checklist

• No implementation details present
• Requirements are testable and unambiguous
• Success criteria are measurable
• User scenarios cover primary flows
• Edge cases identified
• Scope clearly bounded

Success Criteria Quick Reference

Good (User-focused, Measurable, Technology-agnostic)

• "Users complete checkout in under 3 minutes"
• "System supports 10,000 concurrent users"
• "95% of searches return results in under 1 second"

Bad (Implementation-focused, Internal metrics)