By tercel
Generate and maintain professional software specifications — from idea validation to PRD, SRS, technical design, feature specs, test cases, review, audit, analysis, and propagation — based on industry standards.
Use when analyzing a document collection to map themes, find conflicts, gaps, and redundancies — generates landscape analysis report
Use when auditing existing project docs for quality, completeness, and code alignment — generates findings report with fix recommendations
Use when a project may need splitting into sub-features — analyzes scope and generates feature manifest with dependencies
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
Analyze a collection of documents to build a knowledge map, identify themes, find gaps, duplicates, conflicts, and staleness, then produce an organized analysis with improvement recommendations. Designed for document ecosystems (cross-repo docs, research collections, mixed-format doc repos) where the challenge is understanding the landscape, not auditing against code.
Audit existing project documentation for quality, completeness, consistency, and code alignment. Scans docs against the actual codebase to find stale references, missing coverage, internal contradictions, and quality issues. Generates a structured findings report with severity levels and actionable fix recommendations. Works on any project with a docs/ directory.
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.
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 auto chain (idea → decompose → tech-design + feature specs).
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.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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.
Software projects need clear specifications. spec-forge covers the full journey from idea to implementation-ready documents:
| Command | Description | Standards |
|---|---|---|
/spec-forge:idea <name> | Interactive brainstorming — explore and refine ideas | — |
/spec-forge:decompose <name> | Decompose project into sub-features | — |
/spec-forge:tech-design <name> | Technical Design Document + auto-generated feature specs | Google Design Doc, RFC Template |
/spec-forge <name> | Full chain — auto-run Idea → Decompose → Tech Design + Feature Specs → Review | All of the above |
/spec-forge:review <name> | Review generated specs for quality & consistency, auto-fix issues | — |
/spec-forge:prd <name> | Product Requirements Document (on-demand) | Google PRD, Amazon PR/FAQ |
/spec-forge:srs <name> | Software Requirements Specification (on-demand) | IEEE 830, ISO/IEC/IEEE 29148 |
/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.
/spec-forge:idea <name> — BrainstormingInteractive, multi-session brainstorming for early-stage ideas:
ideas/ directory (add to .gitignore or commit for team use)/spec-forge:idea cool-feature # Start or resume brainstorming
/spec-forge:idea # List all ideas
Status flow: exploring → researching → refining → ready → graduated (or parked at any stage)
/spec-forge <name> — Full ChainRun the streamlined specification chain in one command:
/spec-forge user-login # Auto: Idea → Decompose → Tech Design + Feature Specs
docs/features/ (Step 7 of tech-design)ideas/, uses it as requirements context/spec-forge:decompose <name> — Project DecompositionAnalyze project scope and split into sub-features if needed:
/spec-forge:decompose my-project # Interview → split analysis → manifest
docs/project-{name}.md manifest for multi-split projects/spec-forge <name> full chain (after Idea, before Tech Design)/spec-forge:prd <name>Generates a Product Requirements Document including:
Reference: Google PRD, Amazon Working Backwards (PR/FAQ), Stripe Product Spec
npx claudepluginhub tercel/tercel-claude-plugins --plugin spec-forgeComplete development workflow — from TDD-driven implementation plans to execution, debugging, code review, git worktree management, branch lifecycle, and parallel agent dispatch
Project Due Diligence & Investment Analysis Skill — perform deep technical and business analysis on open-source projects, startups, and SaaS products to generate structured due diligence reports.
Technical Evangelist & Growth Skill — transform code and projects into high-impact content for developer platforms (Dev.to, Hashnode, X.com, Hacker News, Reddit).
Specification-driven development workflow: specify → plan → tasks → implement
Spec-driven development with search, conflict detection, and reporting
Spec-driven development methodology for Claude Code. Provides skills for requirements engineering (EARS format), design documentation, task breakdown, AI prompting strategies, quality assurance, and troubleshooting.
Specification-Driven Development with Process Discipline for Claude Code
AI-assisted spec crafting through research, interviews, and multi-LLM review. Like Geppetto carved Pinocchio from wood, transform rough ideas into living implementation plans.
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.