← ClaudeAtlas

spec-forgelisted

Professional specification system for Codex. Use when the user asks to create, improve, review, audit, analyze, or propagate product/software documentation, including requirements documents to hand to an implementation team or vendor, SRS/functional/non-functional requirements, PRDs and business cases, ideas, technical designs, architecture/RFC docs, feature specs, test cases, documentation audits, document landscape analysis, and full idea-to-spec chains. The chain's spine is a delivery-grade requirements spec followed by a technical design, handed off to code-forge for implementation: [idea] -> [decompose] -> [prd] -> srs -> tech-design -> review.
tercel/spec-forge · ★ 9 · Testing & QA · score 77
Install: claude install-skill tercel/spec-forge
# Spec-Forge Orchestrator Spec-forge is a documentation and specification workflow suite. This root skill is the Codex-facing orchestrator: decide which child skill to load, keep the document chain coherent, and avoid loading large generation references until they are needed. ## Trigger Patterns Use this skill when the user asks for any of the following: - Start or refine an idea before specs: use `skills/idea/SKILL.md` - Split a large project into sub-features: use `skills/decompose/SKILL.md` - Write a PRD, business case, or product definition �� "is this worth building": use `skills/prd-generation/SKILL.md` - Write the requirements a team will be held to — a requirements spec, an SRS, functional/non-functional requirements, **a requirements document to hand to an implementation team or vendor**: use `skills/srs-generation/SKILL.md` - Write a technical design, architecture doc, design doc, or RFC: use `skills/tech-design-generation/SKILL.md` - Generate test cases, QA coverage, or a test case matrix: use `skills/test-cases-generation/SKILL.md` - Review spec-forge documents for quality and consistency: use `skills/review/SKILL.md` - Audit project docs against code: use `skills/audit/SKILL.md` - Analyze a document ecosystem for themes, conflicts, gaps, redundancy, or staleness: use `skills/analyze/SKILL.md` - Propagate an upstream doc change downstream: use `skills/propagate/SKILL.md` - Run the full chain for a feature: orchestrate `[idea] -> [decompose] -> [prd] -> srs ->