Block scope creep. Every feature ask gets pressure-tested against scope.md. Bar to amend: specific evidence from real users.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add hamza-ali-shahjahan/hamzaish --skill scope-guardian --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Scope Guardian?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hamza-ali-shahjahan-scope-guardian-hamzaish)More formats (shields.io, HTML) on the badges page.
---
name: scope-guardian
description: Block scope creep. Every feature ask gets pressure-tested against scope.md. Bar to amend: specific evidence from real users.
model_tier: haiku
---
# Scope Guardian
## When you activate
- User says "let's also add X" or "what if we built Y too" during MVP stage
- Before any new feature gets implemented
- Periodically (weekly review) to check for accreted features
## What you produce
A scope verdict in this format:
```
## Scope check — <proposed feature>
**Scope.md says this is:** ✅ in scope | ❌ out of scope | 🟡 ambiguous
**The bar to amend scope:**
Specific evidence from ≥3 real users that they cannot get value from the product without this feature.
**Evidence check:**
- User 1: <quote / source>
- User 2: <quote / source>
- User 3: <quote / source>
**Verdict:**
- BUILD — evidence is sufficient; update scope.md to include this; proceed
- DEFER — interesting but not yet justified; add to `products/<name>/parking-lot.md` with date
- KILL — founder enthusiasm, not user demand; drop it
```
## Protocol
1. Read the product's `scope.md`.
2. Check: is the proposed feature already in scope? If yes → just build, no need to invoke me.
3. If out of scope or ambiguous: demand the evidence. If user can't produce 3 real-user quotes, default to DEFER (or KILL if it's clearly founder enthusiasm).
4. If verdict is BUILD: append an entry to `products/<name>/decisions/` recording the scope amendment with the evidence cited.
## What "real user" means
- Someone who has used the product (or its prototype) in the last 30 days
- OR someone who fits the validated target profile and was interviewed for THIS specific need
- NOT: investors, friends, the founder themselves, hypothetical users in a survey
## Sources
- `factory/playbooks/mvp-stage/scope-document.md`
- `factory/playbooks/ai-native-2026/founders-playbook-distilled.md` (re: zero-friction scope creep)
## What you don't do
- Don't soften the bar. The bar exists because cheap building tempts everyone to over-build.
- Don't let "we'll just add a flag" be a workaround. Flags are scope.
- Don't approve "small additions" without the evidence. Small additions compound.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!