| name | mvp-scope-2h |
| description | Use only at the start of a timed agent-project exam to shrink the prompt into a 2-hour MVP with explicit scope, non-goals, happy path, file tree, and time budget. Not for implementation details. |
| origin | ECC-derived |
MVP Scope 2H
Source Lineage
Primary inherited sources:
legacy/ecc-source/agents/planner.mdlegacy/ecc-source/commands/plan.mdlegacy/ecc-source/rules/common/development-workflow.mdlegacy/ecc-source/skills/search-first/SKILL.mdlegacy/ecc-source/docs/token-optimization.mdlegacy/ecc-source/skills/strategic-compact/SKILL.md
Inherited methods:
- restate the requirement before touching code
- analyze existing structure before proposing changes
- search for reuse before building custom code
- break work into phases with success criteria and risks
- compact context at phase boundaries, not mid-implementation
When To Use
Use this before writing code, right after reading the prompt.
Use it to:
- compress the task into a 2-hour deliverable
- identify the single main loop to build first
- reject tempting but non-essential features
Expected Outputs
- a one-paragraph prompt summary
- chosen success criteria
- explicit MVP scope
- explicit non-goals
- a small target file tree
- a rough time split for the remaining session
Workflow
- Restate the prompt in plain language.
- Identify success criteria, assumptions, and constraints.
- Search the repo and stack for reusable patterns before inventing new code.
- Choose one main path only.
- Convert everything else into explicit non-goals unless the prompt truly requires it.
- Sketch the smallest file tree that can support the main path.
- Reserve time for tests and README before writing implementation code.
Reuse Decision
Use the compressed search-first decision matrix:
Adopt when the repo or stack already has a close match.Extend when an existing pattern covers most of the need.Build only when reuse would take longer than a small custom path.
In an exam, the wrong move is often rebuilding infrastructure the repo already hints at.
Output Format
- Prompt summary:
- Success criteria:
- Main loop:
- MVP scope:
- Non-goals:
- Small file tree:
- Time budget:
Scope Questions
- What is the one user or system action that must work?
- What can be hard-coded, stubbed, or omitted safely?
- What infrastructure is unnecessary for a 2-hour exam?
- Which edge cases can be acknowledged instead of implemented?
What Not To Do
- do not design a platform
- do not start with abstractions or extension points
- do not promise background jobs, admin panels, billing, or rich observability
- do not leave non-goals implicit
- do not let search or planning expand into a research project
