tercel/spec-forge

tercel/spec-forge

Command

Use when analyzing a document collection to map themes, find conflicts, gaps, and redundancies — generates landscape analysis report.

tercel/spec-forge

Command

Use when auditing existing project docs for quality, completeness, and code alignment — generates findings report with fix recommendations.

tercel/spec-forge

Command

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

tercel/spec-forge

Command

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

tercel/spec-forge

Command

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

tercel/spec-forge

Command

Use after editing an upstream doc (PRD/SRS/tech-design/feature-spec) to propagate changes downstream and keep the entire doc chain consistent.

tercel/spec-forge

Command

Use when reviewing spec-forge generated documents for quality, completeness, and consistency — auto-fixes issues if found.

tercel/spec-forge

Command

Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.

tercel/spec-forge

Command

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

tercel/spec-forge

Command

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

tercel/spec-forge

Command

Use when writing test cases, generating tests, supplementing test coverage, or improving test completeness — auto-scans project, designs multi-dimensional test cases with coverage matrix.