skills.rest
rakhnianskii9
rakhnianskii9COMMUNITY
Explore all skills by this author →
GitHub

scope-check

Compares original plan to current code to generate a Markdown report with bloat score.

Updated Apr 24, 2026
Search Tags:#reporting#baseline#risk-assessment#project-management#sprint-planning#scope-creep
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill scope-check-rakhnianskii9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/scope-check
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill scope-check-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scope creep is a pervasive risk in iterative development. This skill automates detection by comparing the original baseline against current work, surfacing additions, deletions, and drift.

Core Features & Use Cases

  • Baseline discovery: locate design/gdd documents and sprint plans to establish the original scope.
  • Change quantification: quantify additions, removals, and modifications to measure drift.
  • Risk-informed recommendations: assess schedule, quality, and integration risks to guide prioritization and cuts.
  • Decision-ready reporting: generate a concise report with a bloat score, actionable items, and next steps.

Quick Start

Provide a feature name or sprint identifier to generate a scope creep report against the 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 detect scope creep in my project?▼

Identify scope creep by comparing original baseline documents against current code changes to measure drift. This generates a Markdown report with a bloat score and actionable recommendations to guide re-scoping decisions.

What is the best way to compare current implementation against the original project baseline?▼

Compare current implementation against the original baseline by searching design documents and sprint plans to quantify additions and modifications. This produces a decision-ready report highlighting schedule, quality, and integration risks.

Can I generate a bloat score for a specific feature or sprint?▼

Generate a bloat score for a specific feature by providing its name or sprint identifier. The analysis searches baseline documents and current code changes to calculate the score and produce structured pruning recommendations.

How do I assess schedule and integration risks when trimming project scope?▼

Assess schedule and integration risks by validating detected scope changes against original milestones and sprint plans. This yields risk-informed recommendations that help prioritize cuts and guide re-scoping decisions effectively.

Does scope creep detection work without dedicated baseline documents?▼

Scope creep detection relies on locating baseline documents like design specs or production sprints to establish the original plan. Without these foundational baseline documents, accurately quantifying drift and generating a bloat score is not possible.

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
pixel-cellarpixel-cellar
277

sprint-plan

Generate or update sprint plans from milestones, completed work, and capacity.

Official
Intermediate
wojonswojons
4

test-coverage

Measure and report multi-dimensional test coverage across code, requirements, risks, and scenarios.

Community
Intermediate