Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/scope-check
Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts.
Passed 16 of 20 test cases with the skill, and 7 of 20 without it.
and 13 more in the full report
12 fixed4 passed either way1 still failing3 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
List the four numbered recommendation categories used in Phase 3 of the scope check report in their required order.
| Checked | Without skill | With skill |
|---|---|---|
| Lists the four recommendation categories in order: Cut, Defer, Keep, and Flag. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill is read-only — it reports findings but writes no files.
Compares original planned scope against current state to detect, quantify, and triage scope creep.
Argument: $ARGUMENTS — the whole string: a feature name (it may be several words), sprint number, or milestone name.
Locate the baseline scope document for the given argument:
design/gdd/[feature].md or matching file in design/sprint-3) → read production/sprints/sprint-003.md (the name /sprint-plan writes) or similarproduction/milestones/[name].mdIf the document is not found, report the missing file and stop. Do not proceed without a baseline to compare against.
Check what has actually been implemented or is in progress:
git log --oneline --since=[start-date])Produce the comparison report:
test cases passed, vs 7 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.