Analyze
Skill pooyagolchian/specforge/plugins/specforge/skills/analyze
Cross-check a feature's spec, plan, and tasks for consistency, coverage, and drift before implementing. Use when the user wants to analyze, verify, or validate the artifacts, check requirement coverage, or find gaps between spec/plan/tasks. Read-only report; does not modify code.From its SKILL.md
npx -y skills add pooyagolchian/specforge --skill analyzeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.1 KB, 451 tokens by cl100k_base, as published. Nobody here has run it
/specforge:analyze — consistency & coverage check
Audit the active feature's artifacts against each other and report gaps. Read-only — it produces
findings, it does not change code. Delegate to the reviewer subagent for an independent pass.
When to use
- After
/specforge:tasks, before/specforge:implement. - Whenever the user wants to confirm the spec, plan, and tasks agree.
Checks to run
- Requirement coverage: every
FR-xxx/NFR-xxxinspec.mdmaps to a design element inplan.mdand to at least one task intasks.md. List any unmapped requirement. - No orphan work: every task traces back to a real requirement. Flag tasks with no
→ FR-xxx. - Constitution compliance: the plan's Constitution Check covers each principle (or documents an exception). Flag missing ones.
- No leaked HOW in the spec and no unresolved
[NEEDS CLARIFICATION]remain. - Tech-environment compliance: the plan uses no prohibited library and matches the declared language/framework.
- Contracts present for any external interface the spec implies.
Output
Write a short findings report to specforge/specs/NNN-slug/analysis.md (and summarize inline):
# Analysis: <name> — <date>
## Coverage
- FR-001 → plan §3 → T020 ✅
- NFR-002 → (no task) ⚠️ GAP
## Issues
- [severity] <finding> → <suggested fix>
## Verdict
Ready to implement | Needs fixes: <list>
Then update specforge/state.md (| NNN-slug | analyze | done | <date> |) and append an audit
row. If gaps exist, recommend returning to the relevant stage before approving.
Guardrails
- Do not fix code here — this stage only surfaces gaps.
- Be specific: cite the requirement ID, the file, and the missing link.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.