| name | idea_to_action |
| description | Transforms abstract ideas into execution-ready systems. Follows the Brainstorm → Filter → Execute pipeline with a "Reality-First" founder mindset. |
Idea to Action
Use this skill when the user has a raw idea and wants to convert it into a concrete, executable plan.
Core Philosophy
- Brainstorm → Filter → Execute: Don't just list ideas; curate them for viability.
- From Zero to System: Move from "what if" to "how it works".
- Think Like a Founder: Focus on ROI, feasibility, and speed to market.
- Reality-First Mode: Ignore the hype; focus on what is actually buildable today.
Inputs
- The Idea: The raw concept or "What if..." statement from the user.
Workflow
Phase 1: The Founder's Summary
- Input: Listen to the user's raw idea.
- Action: Summarize the core value proposition.
- Constraint: Filter out feature creep. focus on the specific problem being solved.
- Output: A clear, concise statement of "What is this?" and "Why does it assume it will work?"
Phase 2: Deep Dive (System Architecture)
- Action: Expand the summary into a system view.
- What are the moving parts?
- What are the inputs and outputs?
- What is the "secret sauce" or key differentiator?
Phase 3: The Execution Plan
Convert the system view into actionable steps. Provide the following sections:
- Actionable Steps: A checklist of 5-10 concrete items to start right now.
- Schedule: A tentative timeline (e.g., "Day 1: Prototype", "Day 3: User Tests").
- Risk Analysis:
- Technical Risks: What might break?
- Market/Product Risks: Will anyone care?
- Multilevel Explanations:
- The Pitch (ELI5): How to explain it to a 5-year-old (or an investor).
- The Specs (Technical): How to explain it to an engineer.
Advanced Ideation Framework (Divergent & Convergent)
If the idea is still vague or needs stress-testing, apply this structured process:
- Understand & Expand (Divergent): Restate the idea as a crisp "How Might We" statement. Ask sharpening questions (Who is this for? What does success look like?). Generate variations using lenses like Inversion, Constraint Removal, and 10x Scale.
- Evaluate & Converge: Cluster the generated ideas into distinct directions. Stress-test each direction against User Value, Feasibility, and Differentiation.
- Surface Hidden Assumptions: Explicitly name what you are betting is true, what could kill the idea, and what you are choosing to ignore.
- The "Not Doing" List: Produce a concrete MVP scope, but more importantly, list what is explicitly NOT being built and why. Focus is about saying no to good ideas.
