fp-delete-scope

FP: Delete Scope

Delete before architecture.

This skill takes the real goal from question-requirements and reduces it to the smallest verifiable MVP.

It uses:

• first-principles reasoning
• Occam's Razor
• MVP-first scope cutting
• early decoupling boundaries

Do not design the full system while using this skill. Do not write code while using this skill.

---

When to use

Use this skill after question-requirements when:

• the real goal has been identified,
• the task has more than one possible implementation,
• the request contains nice-to-have work,
• the agent may add premature abstractions,
• the task may sprawl across modules,
• the user wants an MVP,
• the architecture should stay decoupled.

For tiny edits, do not run the full process.

---

Core principles

1. First principles

Keep only what is necessary to satisfy the real goal.

Ask:

What must be true for the user outcome to be achieved?
What capability is irreducible?
What evidence proves that the outcome exists?
What is merely an implementation assumption?

2. Occam's Razor

Do not add entities without necessity.

An entity can be a feature, command, file, module, abstraction, adapter, workflow, automation, runtime, state file, database, agent role, example, test surface, or documentation page.

If the MVP still works without it, delete or defer it.

3. MVP before architecture

Do not design the full system before the minimum useful version is defined.

Architecture should be based on the MVP, not on imagined future scale.

---

Required input

Use the output from question-requirements if available:

• likely real goal
• success criteria
• failure paths
• assumptions
• non-goals
• decision

If the real goal is still unclear, stop and return:

Decision: ask_user
Reason: delete-scope requires a clarified real goal.
Smallest useful question: ...

---

Procedure

1. Restate the real goal

Use the clarified goal from question-requirements.