Compare original plans against current implementation to quantify scope creep.
npx skills add https://github.com/emcconnell/nova-scout --skill scope-check-emcconnell
Please help me install this Agent Skill. Skill: scope-check Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/scope-check Command: npx skills add https://github.com/emcconnell/nova-scout --skill scope-check-emcconnell
This Skill identifies additions to a feature or sprint that were not in the original plan, quantifies net scope change, and highlights items that increase schedule, quality, or integration risk so teams can triage and re-scope confidently.
Run scope-check on sprint-3 to compare the sprint plan with the current repository files and git history and produce a scope creep report.
High-intent search queries and answers about installing and using this skill.
To quantify scope creep in a sprint, compare original plans against current implementation by analyzing the codebase, git history, and design docs to produce a bloat score and itemized additions or removals.
A bloat score is a quantified metric of net scope change generated by comparing baseline feature design documents against current codebase commits to highlight items increasing schedule, quality, or integration risk.
Yes, you can scan git commits and TODO or FIXME markers in the codebase to enumerate implemented or in-progress items, enabling effective triage by identifying unplanned additions introduced during a sprint review.
No, scope-check requires read-only access to repository files, design and production docs, and git history to evaluate additions, removals, and unfinished tasks without modifying the codebase.
To get prioritized recommendations for cutting or deferring scope, analyze itemized additions and removals with their effort estimates and risk assessment to determine which unplanned items to keep or cut to meet deadlines.
polseguCompare current implementation and active work against original scope plans.
johnatas-henriqueDetect and quantify scope creep by comparing planned scope against implemented state.
djd1mGenerate sprint-ready task lists from roadmap and git history, respecting dependencies and flagging incomplete work for review.
tylerburleighCompare code implementations against specifications and categorize deviations.
