skill-scope-drift
Scope Drift Detection
Compares the actual code diff against stated intent (TODOS.md, PR description, commit messages) to surface scope creep and missing requirements before the full code review runs.
This is informational only — it never blocks a review or merge. Some scope drift is intentional ("I saw a bug while working on the feature"). The goal is awareness, not enforcement.
When to Run
- Automatically as part of
/octo:deliverand/octo:review(Dev context only) - Manually via: "check scope drift", "scope check", "did I drift?"
- Skipped for Knowledge context reviews (no diff to compare)
How It Works
Step 1: Gather Stated Intent
Collect intent signals from multiple sources (any that exist):
More from nyldn/claude-octopus
octopus-architecture
System architecture and API design with multi-AI consensus — use for design reviews and new subsystems
18skill-code-review
Expert multi-AI code review with quality and security analysis
16skill-intent-contract
Lock in user goals upfront and validate outputs against them — use to prevent scope drift
15skill-prd
Write an AI-optimized PRD using multi-AI orchestration — use when scoping a new feature or product
14skill-knowledge-work
Switch to Knowledge Work mode for research and writing — use when task is non-code focused
14skill-extract
Reverse-engineer design systems, tokens, and components from live products or screenshots
14