Compare baseline scope documents against codebase state to quantify scope creep.
npx skills add https://github.com/scomofo/dragon-forge --skill scope-check-scomofo
Please help me install this Agent Skill. Skill: scope-check Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/scope-check Command: npx skills add https://github.com/scomofo/dragon-forge --skill scope-check-scomofo
Scope-check helps teams detect and quantify scope creep by comparing the original planned work against what is currently implemented or in progress.
Run scope-check for the relevant sprint or feature name (for example, scope-check sprint-04) to generate a scope creep report with a PASS/CONCERNS/FAIL verdict.
High-intent search queries and answers about installing and using this skill.
Scope creep detection works by loading a baseline sprint plan or feature design document, scanning the codebase for related changes, and comparing the original plan against the current implemented state to quantify unplanned additions.
A scope creep risk assessment evaluates whether a team is adding unplanned deliverables without corresponding cuts or timeline changes during workflow reviews, producing a quantified comparison and concrete recommendations on what to cut, defer, keep, or flag.
Run the scope-check command for the relevant sprint or feature name, such as sprint-04. The tool inspects repository evidence including commit history and codebase scans, then produces a report with a bloat score, risk assessment, and a canonical PASS, CONCERNS, or FAIL verdict.
Yes, current-state inspection scans the codebase for related changes and looks for indicators like TODO and FIXME markers alongside active sprint plan updates to measure unplanned work and calculate a bloat score against the original plan.
The best way to perform engineering triage is to compare the original planned work against the in-progress state to produce actionable recommendations, yielding concrete cut, defer, keep, and flag decisions based on a quantified risk assessment.
No, baseline discovery is required because the tool must read the original expected design or production documents to establish the planned work, which is then compared against the current implemented state to identify and quantify deviations.
polseguCompare current implementation and active work against original scope plans.
nesnilnehcMap backlog items to strategic anchors and generate a Backlog Alignment Report.
imclabGenerate sprint plans with acceptance criteria and gating checks.
MichaelSolatiCompare planned scope against git history and codebase to quantify scope creep.
