Validate that requested work stays inside the active spec boundary.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add Eliyce/paqad-ai --skill scope-check --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Scope Check?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/eliyce-scope-check)More formats (shields.io, HTML) on the badges page.
---
name: scope-check
description: Validate that requested work stays inside the active spec boundary.
model_tier: fast
triggers:
- workflow:
- feature-development
- bug-fix
- refactor
- migration
cacheable: false
cache_key_inputs: []
output_format: markdown
input_schema:
request_text:
type: string
required: true
description: Incoming request to validate against the active spec.
spec_paths:
type: path[]
required: true
description: Active spec artifacts that define the approved scope.
---
## What It Does
Checks whether the requested change is already authorized by the active spec so implementation does not drift into unspecced work.
## Use This When
Use this before implementation, refactors, or bug fixes that could quietly expand scope beyond the approved story or solution artifact.
## Inputs
- Read the request text at `request_text`.
- Read every active spec artifact passed in `spec_paths`.
- Read `references/scope-rules.md` before deciding whether the request is covered, additive, or out of scope.
## Procedure
1. Run `scripts/check-spec-presence.sh` — exit 1 means immediately classify as `blocked-no-spec` and stop.
2. Extract requested behavior change, modules, and constraints from the request.
3. Compare against the active spec artifacts only (no inferred memory, no informal context).
4. Pick a decision from `assets/decision-vocabulary.txt` (`within-scope | extension-needed | blocked-no-spec`).
5. Cite exact spec evidence (file + criterion/passage).
6. Format per `assets/output.template.md`; validate with `scripts/lint-output.sh`.
## Output Contract
- Match `assets/output.template.md`: `## Scope Decision` (decision token + one-line justification), `## Spec Evidence`, `## Required Next Step`.
- Decision token must come from `assets/decision-vocabulary.txt`.
- Output must pass `scripts/lint-output.sh` (exit 0).
## Escalate / Stop Conditions
- Block when no spec artifact exists for feature, bug-fix, refactor, or migration work.
- Ask when multiple spec artifacts conflict or define incompatible boundaries.
- Do not grant scope based on an unstated workflow or informal memory.
## Resources
- `references/scope-rules.md`
- `scripts/check-spec-presence.sh`
- `scripts/lint-output.sh`
- `assets/output.template.md`
- `assets/decision-vocabulary.txt`
- `.paqad/`
- `agents/openai.yaml`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!