skills.rest
quangkmhd
quangkmhdCOMMUNITY
Explore all skills by this author →
GitHub

scope-check

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

Updated Apr 25, 2026
Search Tags:#planning#backlog#scope#risk-management#sprint#scope-creep
One-click install
npx skills add https://github.com/quangkmhd/Vietstock_Agent --skill scope-check-quangkmhd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/quangkmhd/Vietstock_Agent/tree/main/.agents/skills/scope-check
Command: npx skills add https://github.com/quangkmhd/Vietstock_Agent --skill scope-check-quangkmhd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams and project leads identify scope creep by comparing the current work against the original plan. It flags additions, quantifies bloat, and suggests cuts to keep delivery on track.

Core Features & Use Cases

  • Compare baseline scope against current implementation using design docs, sprint plans, and milestones.
  • Generate a structured report with original scope, current scope, additions, and removals.
  • Produce risk and impact assessments to guide decision-making.

Quick Start

Provide a feature name or sprint identifier to run a scope check 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 current sprint compared to the original plan?▼

Detect scope creep by comparing current implementation against baseline documents in design and production folders. This generates a structured report detailing additions, removals, and a bloat score.

What is the best way to quantify project bloat and assess delivery risks?▼

Quantify project bloat and assess delivery risks by generating a scope comparison report. This evaluates baseline against current scope to produce a bloat score and specific risk impact assessments.

Do I need baseline design documents and sprint plans to run a scope review?▼

Yes, baseline documents located in design or production directories are required to run a scope review. The tool compares these original sprint or milestone plans against current scope to detect changes.

Can I use this to check if feature scope is changing during stakeholder meetings?▼

Yes, you can check if feature scope is changing during stakeholder meetings by running a scope check. It provides immediate addition reports, bloat scores, and risk assessments to guide scope conversations.

What limitations exist when tracking milestone scope changes without baseline files?▼

Tracking milestone scope changes without baseline files is not possible because the comparison requires original design and production documents. Without these baselines, the tool cannot calculate bloat scores.

Related Skills

Explore More Product & Management Skills→
WindXRanWindXRan

scope-check

Compare planned baselines against current codebase state to detect scope creep.

Community
Intermediate
qa-amanqa-aman
19

milestone-scoping

Classify milestone scope into Must, Should, and Cut within a fixed time window.

Community
Advanced
tylerburleightylerburleigh
4

sdd-fidelity-review

Compare code implementations against specifications and categorize deviations.

Community
Intermediate
johnatas-henriquejohnatas-henrique

scope-check

Detect and quantify scope creep by comparing planned scope against implemented state.

Community
Intermediate