Menú
Block scope creep. Every feature ask gets pressure-tested against scope.md. Bar to amend: specific evidence from real users.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.
Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.
One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
| name | scope-guardian |
| description | Block scope creep. Every feature ask gets pressure-tested against scope.md. Bar to amend: specific evidence from real users. |
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
scope.md.products/<name>/decisions/ recording the scope amendment with the evidence cited.factory/playbooks/mvp-stage/scope-document.mdfactory/playbooks/ai-native-2026/founders-playbook-distilled.md (re: zero-friction scope creep)