skills.rest
kay6198835
kay6198835COMMUNITY
Explore all skills by this author →
GitHub

scope-check

Compares planned scope with current implementation to produce a bloat score and risk assessment.

Updated Feb 8, 2024
Search Tags:#planning#scope#risk-assessment#report#sprint#scope-creep
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill scope-check-kay6198835
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/scope-check
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill scope-check-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify scope creep by comparing the originally planned scope with the current implementation, flagging additions and quantifying changes.

Core Features & Use Cases

  • Find the Original Plan, Read the Current State, and Compare Original vs Current Scope to generate a structured scope-check report.
  • Provide a Bloat Score, Risk Assessment, and concrete Recommendations to keep projects on track.
  • Use Case: during feature development or sprint reviews when stakeholders ask "are we still in scope?"

Quick Start

Use a target like sprint-03 or feature-xyz to 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 detect scope creep during sprint planning?▼

Detect scope creep by comparing original planned scope to current implementation. This skill analyzes baseline design and sprint documents against codebase changes to generate a structured report with a bloat score and risk assessment.

What is a bloat score and how is it calculated for feature development?▼

A bloat score quantifies scope creep by measuring additions beyond the original plan. This skill calculates it by analyzing codebase changes and commit history, comparing them against baseline documents to flag bloat and recommend cuts.

How do I generate a risk assessment report for unapproved project additions?▼

Generate a risk assessment by evaluating current implementation against the original planned scope. This skill produces a structured report flagging scope creep additions and providing concrete recommendations to keep projects aligned.

What documents do I need to perform a scope creep analysis?▼

You need access to baseline design and sprint documents to perform scope creep analysis. The skill requires these original planned scope documents to compare against current codebase changes and commit history for generating the bloat score.

Can I review milestone progress and check if we are still in scope?▼

Review milestone progress by comparing the original planned scope to the current implementation state. The skill applies to milestone reviews and sprint planning, producing a structured scope-check report to quantify additions and flag bloat.

When should I use a scope creep report instead of manual project tracking?▼

Use a scope creep report when stakeholders ask if development is still in scope during feature development or sprint reviews. It provides automated bloat scoring and risk assessment by analyzing codebase changes against baseline design documents.

Related Skills

Explore More Product & Management Skills→
quangkmhdquangkmhd

scope-check

Compare current sprint scope against baseline documents to identify additions and removals.

Community
Advanced
HechaoYannetHechaoYannet

scope-check

Compare original project plans against current development to quantify scope creep.

Community
Advanced
AcendasAcendas
2

ship-quick

Apply small code changes with test-first validation and a single auditable commit.

Official
Intermediate
mmcmediammcmedia
2

tech-lead

Coordinate technical projects across PsalMix, n8n workflows, and dashboards.

Community
Advanced