skills.rest
onemanking
onemankingCOMMUNITY
Explore all skills by this author →
GitHub

scope-check

Compares current implementation scope against original plans to detect and quantify scope creep.

Updated Apr 13, 2026
Search Tags:#project management#scope creep#risk assessment#git history#sprint analysis#game production#bloat score
One-click install
npx skills add https://github.com/onemanking/the-operator --skill scope-check-onemanking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/scope-check
Command: npx skills add https://github.com/onemanking/the-operator --skill scope-check-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature work often grows beyond the original plan without anyone noticing until deadlines slip. This Skill compares what was planned against what is actually being built, quantifies the difference, and recommends what to cut, defer, or keep. ## Core Features & Use Cases - Plan vs. Reality Comparison: Reads the original design doc, sprint plan, or milestone definition and compares it against the current codebase, git history, and TODO comments. - Quantified Bloat Score: Reports original item count, current item count, additions, removals, and net scope change as a percentage. - Risk Assessment & Verdict: Rates schedule, quality, and integration risk, then issues a verdict from On Track to Out of Control. - Use Case: Before a sprint review, run the check on Sprint 3 to discover the team added 8 unplanned items (+40% scope), then get a prioritized list of cuts to bring the sprint back on schedule. ## Quick Start Ask the assistant to run a scope check on a feature name or sprint number, such as checking whether sprint 3 has drifted from its original plan.

Frequently Asked Questions about scope-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check a sprint for scope creep?▼

Invoke the scope check with a sprint number, and it reads the sprint plan from production/sprints, scans the codebase and git log for actual work, then reports additions, removals, and a bloat percentage with a verdict.

How is scope creep quantified in the report?▼

The report counts original planned items versus current items, lists each addition and removal in tables, and computes net scope change as a percentage. Verdicts range from On Track under 10% growth to Out of Control above 50%.

What documents does the scope check need to work?▼

It needs an original plan document: a design doc in design/gdd for features, a sprint plan in production/sprints for sprints, or a milestone definition in production/milestones. Without a baseline plan, no comparison is possible.

Does the scope check treat all additions as bad?▼

No. The rules state that some additions are discovered requirements, but they must be acknowledged and accounted for. Recommendations separate items to cut, defer, keep, or flag for a producer decision.

When should I run a scope check during production?▼

Run it mid-sprint or before sprint reviews and milestone deadlines, when there is still time to cut or defer items. It is most useful when git history and in-progress work exist to compare against the plan.

Related Skills

Explore More Product & Management Skills→
tranhieutttranhieutt
70

scope-check

Compare implemented work to sprint or feature plans to detect undeclared scope changes.

Community
Advanced
thecomputer07thecomputer07

qsd-review-backlog

Identify backlog items from ROADMAP and backlog directories for review.

Community
Intermediate
taracodlabstaracodlabs
779

greynoise

Classify IP addresses as scanners or targeted attackers using GreyNoise.

Official
Intermediate
Fantasia1999Fantasia1999

scrum-master

Analyze sprint data with Python scripts for forecasting and health scoring.

Community
Advanced