skills.rest
pixel-cellar
pixel-cellarOFFICIAL
Explore all skills by this author →
GitHub

scope-check

Compares implemented code and plans to report added scope items and pruning recommendations.

277|65|Updated Mar 30, 2026
Search Tags:#release-management#risk-assessment#project-management#sprint-planning#decision-support#scope-creep#design-documents
One-click install
npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill scope-check-pixel-cellar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/pixel-cellar/Claude-Code-Game-Studios/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill scope-check-pixel-cellar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This feature analyzes scope creep by comparing the current scope against the original plan, helping teams identify divergence early.

Core Features & Use Cases

  • Compare original scope (planned features) with the current implementation across code, design docs, and milestones.
  • Quantify expansion and tag items that fall outside the initial plan, with impact estimates and risk signals.
  • Generate actionable pruning recommendations to keep projects focused and on schedule.

Quick Start

Provide the feature name or sprint identifier and let scope-check generate a scope creep report.

Frequently Asked Questions about scope-check

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

FAQPage Schema
How do I identify scope creep by comparing implemented code against original design documents?▼

Scope creep analysis compares current implementation against original design documents and production plans. It identifies added items, estimates their impact, and recommends pruning to keep sprints focused.

What is the best way to detect unplanned features added during sprint planning?▼

Detecting unplanned features involves reading sprint plans and milestone definitions to identify divergences. It quantifies expansion and tags out-of-scope items with risk signals to maintain project focus.

How do I generate a scope creep report for a specific feature or sprint?▼

Generating a scope creep report requires providing the feature name or sprint identifier. The tool analyzes planned versus implemented scope to produce actionable pruning recommendations and impact estimates.

Can I use design docs and milestone definitions to assess project risk and scope divergence?▼

Yes, you can use design docs and milestone definitions to assess project risk. Comparing them against implemented code highlights scope divergence and produces risk signals for items outside the initial plan.

What are the limitations of using scope creep analysis for release management?▼

Scope creep analysis relies on reading existing design documents, sprint plans, and milestone definitions. It is limited by the accuracy of these original plans and requires implemented code to compare against for effective pruning recommendations.

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
sethdfordsethdford
2

Sprint Planning Assistant

Generate sprint plans and risk assessments from team capacity and velocity.

Community
Advanced
zh-xxzh-xx
159

legal-risk-visualization

Extract, categorize, and visualize legal risks with structured charts and diagrams.

Community
Advanced
tygwantygwan
1

sprint

Control sprint lifecycles and track velocity and burndown metrics.

Community
Basic