From specforge
Trigger whenever the user asks to check, validate, or audit connections between requirements artifacts. This includes: cross-reference checking between screens, specs, and use cases; building traceability matrices; finding orphaned or unlinked specs, stories, or epics; generating coverage reports; or asking questions like 'what's missing', 'what's not covered', 'is everything linked', 'are requirements covered', 'find gaps', 'check my cross-references', or 'what specs don't have stories yet'. Use for any verification of existing spec-to-delivery linkage — not for creating or writing new specs, stories, or use cases. Also use before sprint starts to verify story-to-spec traceability, or after creating new specs to check they're properly linked. Provides forward/backward traceability rules, cross-reference validation, coverage metrics, orphan detection, broken reference scanning, and structured reporting.
npx claudepluginhub nguyendlp/specforgeThis skill uses the workspace's default tool permissions.
You are verifying requirements traceability and cross-reference integrity for specifications and delivery artifacts.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
You are verifying requirements traceability and cross-reference integrity for specifications and delivery artifacts.
Business Requirement → Spec (UC/O/S/BR/NFR) → Epic → User Story → Test/AC
User Story → Epic → Spec (UC/O/S/BR) → Business Requirement → Stakeholder
See validation-rules.md for the complete set of cross-reference rules organized by layer and severity.
See scanning-patterns.md for Glob patterns and code regex to discover and index all artifacts.
Report findings as a structured table:
## Traceability Report
### Summary
| Metric | Value |
|---|---|
| Specs scanned | NN |
| Delivery artifacts scanned | NN |
| Cross-references validated | NN |
| Errors found | NN |
| Warnings found | NN |
### Errors (must fix)
| Rule | Source | Issue | Fix |
|---|---|---|---|
| UC-OBJ | UC0005 | No Related Objects listed | Add Related Objects section |
### Warnings (should fix)
| Rule | Source | Issue | Suggestion |
|---|---|---|---|
| UC-EPIC | UC0003 | No epic references this UC | Create EPIC or defer explicitly |
### Orphans
| Type | Code | File | Issue |
|---|---|---|---|
| Spec | BR0005 | BR0005_MaxNesting.md | Not referenced by any UC or Story |
### Coverage
| Metric | Value | Percentage |
|---|---|---|
| UCs with Epics | N / N | NN% |
| Epics with Stories | N / N | NN% |
| Stories with ACs | N / N | NN% |
| BRs referenced by UCs | N / N | NN% |
/check-traceability)Scans all specs and delivery artifacts across the entire docs/ directory. Use when:
When the user specifies a scope (e.g., a single epic, spec, or directory), only scan the relevant artifacts and their direct references. Use when:
For focused checks, still report any broken outbound references (e.g., if the new spec references a UC that doesn't exist), but don't report unrelated orphans.
When a single spec or story was just created, do a lightweight check:
UC0005 but no file with that code existstemplates/software_spec/srs_overview.template.mdtemplates/README.md (two-layer connection guide)