Scope guardian

Skill hamza-ali-shahjahan/hamzaish/_archive/v0/agents/mvp/scope-guardian

Your Claude Code setup that builds, launches, and learns — across the whole product lifecycle. Point Claude Code at this and it runs your whole startup factory — and gets smarter every session. Works with Cursor, Codex & Windsurf too.

Install

npx -y skills add hamza-ali-shahjahan/hamzaish --skill scope-guardian

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Block scope creep. Every feature ask gets pressure-tested against scope.md. Bar to amend: specific evidence from real users.

SKILL.md

2.1 KB, as published. Nobody here has run it

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

Read the product's scope.md.
Check: is the proposed feature already in scope? If yes → just build, no need to invoke me.
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).
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

knowledge-base/mvp-stage/scope-document.md
knowledge-base/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.