spec-forge

Use when a project may need splitting into sub-features — analyzes scope and generates feature manifest with dependencies

Use when creating a feature spec for code-forge — distills requirements into a concise, implementation-ready document

Use when exploring a new idea — validates demand, analyzes competitors, and checks for pseudo-requirements before writing specs

Use when writing a PRD, product spec, or product requirements — follows Google/Amazon/Stripe methodologies

Use when generating software specifications — full chain (PRD→SRS→Tech Design→Test Plan→Feature Spec) or individual documents

Use when writing an SRS, requirements spec, or functional/non-functional requirements — follows IEEE 830 with traceability

Use when writing a tech design, architecture doc, RFC, or design document — follows Google Design Doc format

Use when writing a test plan, test cases, test strategy, or QA document — follows IEEE 829 and ISTQB standards

Lightweight project decomposition skill. Analyzes project scope through a brief interview and determines whether the project should be treated as a single feature or split into multiple sub-features. For multi-split projects, generates a project manifest listing sub-features, dependencies, and execution order.

Generates lightweight, implementation-ready feature specifications. A feature spec is the bridge between spec-forge's formal documentation chain (PRD/SRS/Tech Design/Test Plan) and code-forge's implementation planning. It distills what a module or component must do into a concise, language-agnostic document that code-forge:plan can consume directly. Supports two modes: standalone creation through a brief Q&A interview, or automatic extraction from an existing tech-design document. Output lives in docs/features/ and is shared across all language-specific implementations.

Use when exploring a new idea before writing formal specifications. Guides users through iterative discovery, research, and critical analysis to crystallize vague ideas into validated requirement drafts. Includes anti-pseudo-requirement checks, competitive research, demand evidence gathering, and "What if we don't build this?" analysis. Supports pause/resume across sessions, stores ideas in the project's ideas/ directory, and graduates validated ideas into the spec-forge document chain (/prd → /srs → /tech-design → /test-plan).

Generates professional Product Requirements Documents (PRDs) following industry-standard methodologies. This skill activates when the user asks to write PRD, create a product requirements document, draft product requirements, do product planning, do feature planning, write a product spec, or create a product document. It synthesizes best practices from the Google PRD framework, the Amazon Working Backwards methodology, and the Stripe Product Spec approach to produce comprehensive, actionable PRDs tailored to the user's project.

Generates professional Software Requirements Specification (SRS) documents based on IEEE 830, ISO/IEC/IEEE 29148, and Amazon technical specification standards. This skill activates when the user needs a requirements document, requirements specification, SRS, functional requirements, non-functional requirements, software requirements, requirements analysis, or requirements engineering. It formalizes product needs into structured, testable, and traceable requirements with unique IDs, acceptance criteria, use cases, a CRUD matrix, and a full traceability matrix linking back to the upstream PRD.

Generates professional Technical Design Documents following industry-standard engineering practices. This skill activates when the user asks to write a technical design, create an architecture design, draft a design doc, write a technical proposal, do system design, create a technical design document, write an RFC, create a design document, or produce an architecture document. It synthesizes best practices from the Google Design Doc format, the RFC template structure, and Uber/Meta engineering design standards to produce comprehensive, implementable technical designs tailored to the user's project and codebase.

Generates professional Test Plan and Test Cases documents following IEEE 829 test documentation standards, ISTQB testing methodologies, and Google Testing Blog best practices. This skill activates when the user asks to write a test plan, create test cases, draft a test plan document, create a test cases document, define a test strategy, write a QA document, produce a testing document, draft a test specification, or build a quality assurance plan. It produces comprehensive, structured test documentation that ensures thorough coverage, traceability to requirements, and a clear path from test design through execution and defect management.