Menu
Plan mode on steroids. Push engineers to think with a product mindset before building. Structured intake, then concrete options.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Surprise MVP generator - conceive a novel idea and build a polished MVP without spoiling the surprise
Updates documentation in the repository after completing work. Use when the user explicitly asks to update docs, refresh documentation, or sync docs with code changes.
| name | scope-options |
| description | Plan mode on steroids. Push engineers to think with a product mindset before building. Structured intake, then concrete options. |
Plan mode on steroids. Help engineers think like product people before writing code.
When the user wants to scope a feature before building it. Triggered by /scope-options or when the user asks to think through, scope, or explore options for a feature.
Do a quick, lightweight scan to get the lay of the land:
This should be fast - don't go deep yet. Just enough to have context.
Use AskUserQuestion to get the basic idea:
Just these two questions first. Get the core idea before going deeper.
Now that you know what they want to build, explore the relevant parts of the codebase:
Skip parts of the codebase that aren't relevant to what they're building.
Use AskUserQuestion for remaining questions. Ask in batches of 2-4.
Product questions:
What problem does it solve?
How will we know it's successful?
What's the smallest version that delivers value?
Technical questions:
Any initial ideas on approach?
What are the constraints?
What's the risk if we don't build this?
What are we explicitly NOT building?
Return to the codebase as needed throughout the conversation:
Don't hesitate to explore multiple times. It's better to look things up than to guess.
Present concrete options as soon as you have enough context. Each option should address BOTH product and technical dimensions:
## Option A: [Name]
**What it is:** [1-2 sentence description]
**Product lens:**
- Delivers value to: [who]
- Time to value: [fast/medium/slow]
- Supports future iteration: [yes/no/partially]
**Technical lens:**
- Approach: [brief technical approach]
- Builds on: [existing code/patterns it leverages]
- Effort: [low/medium/high]
**Tradeoffs:**
- Pros: ...
- Cons: ...
---
## Option B: [Name]
...
Always include:
ASCII UI mockups - When the feature involves UI, include simple ASCII mockups to illustrate options:
Option A: Modal approach Option B: Inline approach
┌─────────────────────┐ ┌─────────────────────┐
│ Page content │ │ Page content │
│ │ │ ┌───────────────┐ │
│ ┌───────────┐ │ │ │ Form inline │ │
│ │ Modal │ │ │ │ here │ │
│ │ Form │ │ │ └───────────────┘ │
│ └───────────┘ │ │ │
└─────────────────────┘ └─────────────────────┘
This helps visualize different approaches quickly without building anything.
After presenting options, use AskUserQuestion to:
If conversation gets long, provide a summary:
Once an option is chosen, use AskUserQuestion to ask if they're ready to plan implementation.
If yes, use the EnterPlanMode tool and provide context for the planning phase:
## Planning Context
**Chosen approach:** [Option name and brief description]
**Who it's for:** [from intake]
**Success looks like:** [from intake]
**MVP scope:** [what's in v1]
**Out of scope:** [what we're NOT building]
**Constraints:** [timeline, tech, etc.]
**Relevant existing code:** [what to build on from codebase exploration]
This hands off everything learned during scoping so plan mode can focus on implementation details.
AskUserQuestion