skills.rest
cenconq25
cenconq25COMMUNITY
Explore all skills by this author →
GitHub

scope-check

Compare sprint plans to live work and output a drift summary.

39|6|Updated May 3, 2026
Search Tags:#planning#backlog#scope#sprint#epic#project-management#creep
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill scope-check-cenconq25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill scope-check-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope Check detects sprint scope creep by comparing the original plan to current work, quantifying drift and surfacing a recommended course of action.

Core Features & Use Cases

  • Read the original sprint plan and current live stories to quantify drift and surface actionable recommendations.
  • Compare sprint backlog or epic scope against live work and mid-sprint updates to classify added, expanded, and removed items.
  • Output a read-only drift summary with categorization (Linked/Added/Expanded/Removed) and a recommended next step to regain control.

Quick Start

Run the scope-check mid-sprint to assess drift and surface cut recommendations.

Frequently Asked Questions about scope-check

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

FAQPage Schema
How do I detect sprint scope creep and quantify backlog drift?▼

To detect sprint scope creep, compare your original sprint plan and backlog tables to live stories and mid-sprint updates. This quantifies drift by categorizing backlog items as linked, added, expanded, or removed.

What is the best way to compare epic PRD scope against actual project work?▼

The best way to compare epic PRD scope against actual work is to analyze the drift between planned epic sections and live stories. This surfaces read-only summaries of added or removed items and recommends a corrective action.

How do I identify added or expanded items in a sprint backlog?▼

You can identify added or expanded items in a sprint backlog by reading plan data and current live stories. This classifies changes to surface categorization and recommend next steps to regain project control.

When should I run a scope creep assessment for a sprint-based project?▼

You should run a scope creep assessment mid-sprint to evaluate drift. Reading live stories and mid-sprint updates at this stage quantifies scope expansion and provides recommended cut actions to stay on track.

Does scope checking work with live stories and mid-sprint updates?▼

Yes, scope checking works by reading live stories and mid-sprint updates alongside the original plan. It compares this data to output a drift summary and a recommended action for the sprint backlog.

What limitations exist when analyzing backlog drift in sprint-based projects?▼

A limitation of analyzing backlog drift is that the output is strictly a read-only summary. It surfaces categorization and recommended actions but does not automatically modify or prune the sprint backlog itself.

Related Skills

Explore More Product & Management Skills→
anicdhanicdh

product-owner-review

Classify project plans into user-oriented or technical Epics with dependencies.

Community
Advanced
xloxn69xloxn69
7

agileflow-sprint-planner

Generate a balanced Markdown sprint plan from backlog stories and team capacity.

Community
Intermediate
FrancisVargaFrancisVarga

scope-check

Compare original plans against current code to detect scope creep.

Community
Intermediate
kryptonum-devkryptonum-dev
1

10x-impl-review

Compare repository changes against a plan to identify drift and missing work.

Official
Advanced