spec-diff
/spec-diff
Compares a new request with the current spec to classify coverage or conflict. Use when new work arrives against an existing story or solution and you must decide to continue, extend the spec or stop.
- Author
- eliyce ↗
- Repository
- paqad-ai ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 2
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/extract-ac-ids.sh, scripts/lint-output.sh
What it does and when to use it
Compares a new request with the current spec to classify coverage or conflict. Use when new work arrives against an existing story or solution and you must decide to continue, extend the spec or stop.
Original author description
Compares a new request with the current spec to classify coverage or conflict. Use when new work arrives against an existing story or solution and you must decide to continue, extend the spec or stop.
How it works
- What It Does
- Use This When
- Inputs
- Procedure
- Output Contract
- Escalate / Stop Conditions
- Resources
SKILL.md preview
--- name: spec-diff description: 'Compares a new request with the current spec to classify coverage or conflict. Use when new work arrives against an existing story or solution and you must decide to continue, extend the spec or stop.' metadata: model_tier: medium cacheable: 'false' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Compares an incoming request against the active spec so the framework can tell whether the work is already covered, extends the spec, or conflicts with it. ## Use This When When new work arrives against an existing story or solution and you need to decide whether to continue, extend the spec, or stop because the request conflicts with approved behavior. ## Inputs - Read the incoming request text from `request_text`. - Read the active spec artifacts from `spec_paths`. - Read `references/spec-diff-rules.md` before classifying the request. ## Procedure 1. Run `scripts/extract-ac-ids.sh <spec-paths...>` to load the canonical AC id set. 2. Extract behavior, constraints, and affected modules from the new request. 3. Compare against the active specs only; pick a decision token from `assets/decision-vocabulary.txt`. 4. Cite the exact AC id / passage that supports the call (or note that no AC matches). 5. Format per `assets/output.template.md`; validate with `scripts/lint-output.sh`. ## Output Contract - Match `assets/output.template.md`: `## Spec Diff Decision` (decision token + justification), `## Evidence`, `## Implication`. - Decision token must be `covered | extension | conflict`. - Output must pass `scripts/lint-output.sh` (exit 0). ## Escalate / Stop Conditions - Ask when the active spec set is incomplete or internally contradictory. - Warn when the request implies a behavioral conflict with the accepted solution. - Do not silently respec work that is already covered by the current artifacts. ## Resources - `references/spec-diff-rules.md` - `scripts/extract-ac-ids.sh` - `scripts/lint-output.sh` - `assets/output.template.md` - `assets/decision-vocabulary.txt` - `.paqad/` - `agents/openai.yaml`
Files in this package (8)
- SKILL.md 2 KB
- skill.meta.yaml 1 KB
- agents/openai.yaml 1 KB
- assets/decision-vocabulary.txt 1 KB
- assets/output.template.md 1 KB
- references/spec-diff-rules.md 1 KB
- scripts/extract-ac-ids.sh 1 KB
- scripts/lint-output.sh 1 KB
Versions
The database has no other skills named spec-diff.
Database snapshot: 13.11.2026 · package version ef7e21ffc351 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100spec
Write the spec for a Ready story as its own PR and stop at Spec review. Use when asked to spec a story, write the spec for an issue, or start the next Ready story. Implementing an Approved story is /next. - 100spec-review
对照一份 spec 和一个 git 固定点审已完成的 diff,分 Spec 轴、Standards 轴、证据三块出报告,不改代码。当一份 spec 已实现完、要验收或合并前检查时使用。 - 100spectra-diff
Use this skill when the user asks to: - Compare code against its spec to find drift - Check if spec is still in sync with code - Find new behaviors not documented in spec - Identify spec items that no longer exist in code - Validate spec accuracy after code changes Useful after… - 100to-spec
Turn the current conversation context into a spec and submit it as a GitHub issue. Use when user wants to create a spec or PRD from the current context. - 90to-spec
Turn the current conversation context into an implementation-ready spec or spec set. Use when the user wants to capture a design or implementation plan as a SPEC. - 100to-spec
Turn the current conversation context into a spec. Use when user wants to create a spec (or PRD) from the current context.