spec-forge

Professional Software Specification Generator for Claude Code

Generate industry-standard specifications — from early-stage brainstorming to Technical Design with auto-generated feature specs — each usable standalone or as part of a streamlined auto chain.

Overview

Software projects need clear specifications. spec-forge covers the journey from idea to implementation-ready documents, with one thing at its centre: a requirements specification precise enough to hand to an implementation team and settle acceptance against.

Command	Description	Standards
/spec-forge:srs <name>	Software Requirements Specification — the delivery contract	IEEE 830, ISO/IEC/IEEE 29148
/spec-forge:tech-design <name>	Technical Design Document + auto-generated feature specs	Google Design Doc, RFC Template
/spec-forge <name>	Full chain — [Idea] → [Decompose] → [PRD] → SRS → Tech Design → Review	All of the above
/spec-forge:prd <name>	Product Requirements Document — the business case (conditional)	Google PRD, Amazon PR/FAQ
/spec-forge:idea <name>	Interactive brainstorming — explore and refine ideas	—
/spec-forge:decompose <name>	Decompose project into sub-features	—
/spec-forge:review <name>	Review generated specs for quality & consistency, auto-fix issues	—
/spec-forge:test-cases <name>	Test Cases with coverage matrix (on-demand)	Multi-dimensional coverage
/spec-forge:audit [path]	Audit docs for quality, completeness & code alignment	—
/spec-forge:analyze [path]	Analyze document collection — map themes, find conflicts & gaps	—

Aliases: /prd, /srs, /tech-design, /test-cases, /idea, /decompose, /review, /audit, /analyze work as shortcuts — they invoke each skill directly, bypassing the /spec-forge orchestrator.

Features

• Delivery-grade requirements: The SRS is written to be handed to an implementation team — explicit scope boundaries, field-level input rules, state machines with illegal-transition handling, permission matrix, error catalogue with degradation behavior, and acceptance and change control
• Idea to Spec: Brainstorm interactively, then graduate ideas into requirements, architecture docs, and feature specs
• Full Chain Mode: One command runs [Idea] → [Decompose] → [PRD] → SRS → Tech Design → Review, then hands off to code-forge
• Standalone or Chained: Use any command on its own, or run the full chain for traceability
• Industry Standards: Templates grounded in Google, Amazon, Stripe, IEEE, and ISTQB best practices
• Automatic Context Scanning: Scans your project structure, README, and existing docs before generation
• Project Decomposition: Automatically analyzes scope and splits large projects into sub-features
• Smart Upstream Detection: Finds upstream documents when available; asks compensating questions when not
• Quality Checklists: Built-in 4-tier validation (completeness, quality, consistency, formatting)
• Mermaid Diagrams: Architecture, sequence, user journey, and Gantt diagrams
• Spec Review: Review generated specs for completeness, consistency, and actionability with auto-fix
• Documentation Audit: Cross-reference docs against code for quality, completeness, and consistency
• Document Landscape Analysis: Map, cluster, and evaluate document ecosystems

Commands