role-based-ideation

name	role-based-ideation
description	Role-play as reviewer/practitioner/theorist/novice/competitor to generate diverse perspectives on a solution.
execution	strategy
dependencies	{"sops":["competitor-simulation","novice-perspective","perspective-synthesis","practitioner-hat","reviewer2-hat","theorist-hat"]}

Role-Based Ideation

Role-play as reviewer/practitioner/theorist/novice/competitor to generate diverse perspectives on a solution.

State Ledger

Resource	Target	Current	%
web-search	20	0	0%
web-research	5	0	0%
paper-overview	20	0	0%
paper-search	12	0	0%
paper-research	5	0	0%

HARD-GATE

Cannot exit strategy until ≥80% of each budget line is consumed OR yield targets are met with justification for remaining budget.

Available Tactics

Tactic	Role
perspective-rotation	Rotate through all five role perspectives systematically
evaluation-filtering	Filter and rank resulting ideas (shared)

Available SOPs

SOP	Role
reviewer2-hat	Hostile reviewer perspective
practitioner-hat	Engineer perspective
theorist-hat	Theorist perspective
novice-perspective	Novice perspective
competitor-simulation	Competitor perspective
perspective-synthesis	Synthesize all role outputs

Execution Guidance

1. Reviewer 2: Adopt hostile reviewer stance — find fatal flaws and logical gaps
2. Practitioner: Switch to engineer — assess buildability, cost, timeline
3. Theorist: Adopt theorist role — assess formal foundations and rigor
4. Novice: Become deliberate novice — question every "obvious" assumption
5. Competitor: Become competitor — design strategies to defeat the solution
6. Synthesize: Combine all perspectives into integrated improvement plan

Available SOPs

Optional, no fixed order; the final leaf is always a sop.

SOP	When to use
competitor-simulation	Competitor perspective — design strategies to defeat this solution, then use attack vectors to improve it.
novice-perspective	Novice perspective — question the 'obvious' by adopting deliberate ignorance to reveal hidden complexity.
perspective-synthesis	Synthesize all perspective outputs into a structured multi-perspective idea report.
practitioner-hat	Engineer perspective — assess buildability, cost, timeline, and integration challenges.
reviewer2-hat	Hostile reviewer perspective — find fatal flaws, logical gaps, and missing evidence in a solution.
theorist-hat	Theorist perspective — assess theoretical foundations, formal rigor, and formalization opportunities.