Templates, scripts, and examples for managing feature specifications in specs/ directory. Use when creating feature specs, listing specifications, validating spec completeness, updating spec status, searching spec content, organizing project requirements, tracking feature development, managing technical documentation, or when user mentions spec management, feature specifications, requirements docs, spec validation, or specification organization.
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
README.mdexamples/example-spec-ai-feature.mdexamples/example-spec-complex.mdexamples/example-spec-list.mdexamples/example-spec-simple.mdexamples/example-validation-report.mdscripts/consolidate-specs.shscripts/create-spec-structure.shscripts/create-spec.shscripts/generate-json-output.shscripts/list-specs.shscripts/search-specs.shscripts/update-status.shscripts/validate-spec.shtemplates/archive/plan-template.mdtemplates/archive/project-overview-template.mdtemplates/archive/requirements-template.mdtemplates/archive/spec-metadata.yamltemplates/archive/spec-simple-template.mdtemplates/archive/spec-template.mdCRITICAL: The description field above controls when Claude auto-loads this skill.
Provides comprehensive specification management capabilities including spec creation, status tracking, validation, searching, and template-based documentation. Manages feature specifications in the specs/ directory with consistent numbering, metadata, and status tracking.
scripts/create-spec.sh <spec-name> [description] to create new numbered specsscripts/list-specs.sh [--status STATUS] [--format FORMAT] to list all specsscripts/validate-spec.sh <spec-file> to check spec completenessscripts/update-status.sh <spec-file> <new-status> to change spec statusscripts/search-specs.sh <query> [--section SECTION] to search spec contentSee examples/ directory for detailed usage examples:
example-spec-simple.md - Simple feature specification with basic sectionsexample-spec-complex.md - Complex feature with detailed technical designexample-spec-ai-feature.md - AI/ML feature specification with model detailsexample-validation-report.md - Example validation output with errors and warningsexample-spec-list.md - Example list command output in different formats---
spec-id: 001
title: Feature Name
status: draft
priority: medium
owner: team-name
created: 2025-01-15
updated: 2025-01-15
tags: [category, feature-type]
---
draft → in-progress → review → approved → implemented
↓
rejected
Specs are organized in phase directories based on dependencies:
specs/
├── phase-0/ # Features with no dependencies
│ ├── F001-core-data/
│ │ ├── spec.md
│ │ └── tasks.md
│ └── F002-base-api/
├── phase-1/ # Features depending on Phase 0
│ ├── F003-user-auth/
│ └── F004-chat-system/
├── phase-2/ # Features depending on Phase 1
│ └── F005-analytics/
└── infrastructure/ # Infrastructure specs (not phased)
└── 001-database/
Phase is calculated automatically based on dependencies:
Example: F003 depends on F001 (phase 0) and F002 (phase 0) → F003 is Phase 1
F{XXX}-{feature-slug}/For backward compatibility, the system also supports:
specs/
├── features/
│ ├── 001-feature-name/
│ └── 002-another-feature/
└── infrastructure/
└── 001-component/
The system checks phase-nested first, then falls back to legacy structure.
This skill is used by:
planning:create-spec command - Create new feature specificationsplanning:review-specs command - Review and validate all specsplanning:track-progress command - Track feature implementation progressPurpose: Comprehensive specification management for feature documentation Used by: Planning agents, development teams, project managers