scope-check

Name: scope-check
Availability: InStock
Author: wsman

Compare original plans with current implementations to detect scope creep.

18|5|Updated Nov 25, 2025

Search Tags:#scope creep #risk assessment #git history #sprint review #product planning #feature analysis #baseline comparison

Ready to run

npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill scope-check-wsman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scope-check
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/scope-check
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill scope-check-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you detect when a feature, sprint, or milestone has grown beyond the original plan, so you can catch scope creep early and keep delivery realistic.

Core Features & Use Cases

Baseline Comparison: Compares the original scope document against the current state of work.
Change Detection: Flags additions, removals, and unplanned extras that increase effort.
Risk Triage: Assesses schedule, quality, and integration risk, then recommends what to cut, defer, keep, or flag.
Use Case: A product team is midway through a sprint and suspects the work has expanded; this Skill produces a structured scope review and a clear pass, concern, or fail verdict.

Quick Start

Ask the scope-check skill to review a named feature or sprint against its original plan and return a scope creep verdict with 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 scope creep by comparing the original plan with current implementation?▼

Detect scope creep by comparing baseline documents against repository scanning and git history. This identifies additions, removals, and drift, producing a quantified variance and a clear pass, concern, or fail verdict.

What is the best way to audit a sprint for unplanned feature additions?▼

Sprint audits require baseline comparison against current work to flag unplanned extras that increase effort. This process assesses schedule, quality, and integration risk to recommend what to cut, defer, keep, or flag.

How does git history review help measure project drift during a milestone check?▼

Git history review helps measure project drift by tracking code changes against the original baseline document. It detects TODO items and quantifies variance to reveal exactly how much the implementation has expanded beyond the plan.

Can I assess schedule and integration risk after identifying scope creep?▼

Yes, after identifying scope creep through baseline comparison, you can assess schedule, quality, and integration risk. The analysis provides actionable recommendations on whether to cut, defer, keep, or flag specific features.

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

Feature analysis for scope creep requires original baseline scope documents to compare against the current repository state. This baseline comparison is essential to accurately measure additions, removals, and overall project drift.