Debate Me
Use this skill before implementation when important product or technical choices deserve challenge.
Inputs
Read the user's idea and the smallest relevant project context. Inspect an existing repo only enough to respect its constraints.
Debate Areas
- user/problem clarity and first useful outcome
- MVP cuts and differentiation
- product, UX, operational, data, integration, security, and maintenance risks
- architecture and technical complexity
- team, budget, deadline, platform, and learning constraints
- testing, deployment, and supportability
- need for an experience or technical prototype
Output
Strongest Version of the Idea
A sharper restatement.
Keep in MVP / Cut from MVP
Protect the first useful version.
Biggest Risks
3–7 risks with practical mitigation.
Questions That Materially Change the Build
Only unresolved questions with real consequences.
Recommended Project Setup
Recommend, when relevant:
- product shape and architecture
- platform/runtime and language
- UI/presentation approach
- backend, database/data access, auth/authorization, APIs
- testing and observability
- deployment/environments
- Git workflow, branching, commits, reviews, CI/CD, versioning, releases
For each choice, explain why it fits and label it recommended, not approved.
Prototype Recommendation
State one of:
- no prototype needed
- experience prototype
- technical proof of concept
- architecture/data-flow prototype
- mixed prototype
Define the assumption to validate, cheapest useful format, review criteria, and what must not be mistaken for production code.
Human Choice
Ask the user to choose:
- accept the recommendations
- modify selected choices
- compare alternatives
- leave specific items
TBD
- prototype before deciding
Do not write approved context until the human responds.
Recommended Next Move
Choose prototype, kickstart-pathfinder, to-specs, or pause.
1---2name: debate-me3description: Pressure-test an idea or project and recommend an MVP, technology, delivery workflow, and prototype checkpoint for human selection.4---56# Debate Me78Use this skill before implementation when important product or technical choices deserve challenge.910## Inputs1112Read the user's idea and the smallest relevant project context. Inspect an existing repo only enough to respect its constraints.1314## Debate Areas1516- user/problem clarity and first useful outcome17- MVP cuts and differentiation18- product, UX, operational, data, integration, security, and maintenance risks19- architecture and technical complexity20- team, budget, deadline, platform, and learning constraints21- testing, deployment, and supportability22- need for an experience or technical prototype2324## Output2526### Strongest Version of the Idea2728A sharper restatement.2930### Keep in MVP / Cut from MVP3132Protect the first useful version.3334### Biggest Risks35363–7 risks with practical mitigation.3738### Questions That Materially Change the Build3940Only unresolved questions with real consequences.4142### Recommended Project Setup4344Recommend, when relevant:4546- product shape and architecture47- platform/runtime and language48- UI/presentation approach49- backend, database/data access, auth/authorization, APIs50- testing and observability51- deployment/environments52- Git workflow, branching, commits, reviews, CI/CD, versioning, releases5354For each choice, explain why it fits and label it `recommended`, not `approved`.5556### Prototype Recommendation5758State one of:5960- no prototype needed61- experience prototype62- technical proof of concept63- architecture/data-flow prototype64- mixed prototype6566Define the assumption to validate, cheapest useful format, review criteria, and what must not be mistaken for production code.6768### Human Choice6970Ask the user to choose:71721. accept the recommendations732. modify selected choices743. compare alternatives754. leave specific items `TBD`765. prototype before deciding7778Do not write approved context until the human responds.7980### Recommended Next Move8182Choose `prototype`, `kickstart-pathfinder`, `to-specs`, or pause.