agentleFS
SrejonKhanSrejonKhan/agent-skills/skills/idea_to_action/SKILL.md

idea_to_action

Skill3 starsChanged 2 months agoMITView on GitHub

Transforms abstract ideas into execution-ready systems. Follows the Brainstorm → Filter → Execute pipeline with a "Reality-First" founder mindset.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user has a raw idea and wants to convert it into a concrete, executable plan.

    line 8
  2. Distinctive:

    Brainstorm → Filter → Execute: Don't just list ideas; curate them for viability.

    line 12
  3. Distinctive:

    If the idea is still vague or needs stress-testing, apply this structured process:

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Actionable Steps: A checklist of 5-10 concrete items to start right now.
  2. Schedule: A tentative timeline (e.g., "Day 1: Prototype", "Day 3: User Tests").
  3. Risk Analysis:
    • Technical Risks: What might break?
    • Market/Product Risks: Will anyone care?
  4. 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:

  1. 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.
  2. Evaluate & Converge: Cluster the generated ideas into distinct directions. Stress-test each direction against User Value, Feasibility, and Differentiation.
  3. Surface Hidden Assumptions: Explicitly name what you are betting is true, what could kill the idea, and what you are choosing to ignore.
  4. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.