scope-check

# Scope Check This skill is read-only — it reports findings but writes no files. Compares original planned scope against current state to detect, quantify, and triage scope creep. **Argument:** `$ARGUMENTS[0]` — feature name, sprint number, or milestone name. --- ## Phase 1: Find the Original Plan Locate the baseline scope document for the given argument: - **Feature name** → read `design/gdd/[feature].md` or matching file in `design/` - **Sprint number** (e.g., `sprint-3`) → read `production/sprints/sprint-03.md` or similar - **Milestone** → read `production/milestones/[name].md` If the document is not found, report the missing file and stop. Do not proceed without a baseline to compare against. --- ## Phase 2: Read the Current State Check what has actually been implemented or is in progress: - Scan the codebase for files related to the feature/sprint - Read git log for commits related to this work (`git log --oneline --since=[start-date]`) - Check for TODO/FIXME comments that indicate unfinished scope additions - Check active sprint plan if the feature is mid-sprint --- ## Phase 3: Compare Original vs Current Scope Produce the comparison report: ```markdown ## Scope Check: [Feature/Sprint Name] Generated: [Date] ### Original Scope [List of items from the original plan] ### Current Scope [List of items currently implemented or in progress] ### Scope Additions (not in original plan) | Addition | Source | When | Justified? | Effort | |----------|--------|---...