agentleFS
elvismuslielvismusli/business-validator/skills/brainstorming/SKILL.md

brainstorming

Skill1 starsChanged 9 months agoMITView on GitHub

You MUST use this as the first step before idea-intake — explores and refines the user's raw business idea through collaborative dialogue before structured validation begins

190 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +2 more from Leodorareluctant259
  • +6 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask questions one at a time via AskUserQuestion.

    line 42
  2. Distinctive:

    Start with one open-ended question:

    line 46
  3. Distinctive:

    Ask which resonates most

    line 70
  4. Distinctive:

    Ask: "Does this capture what we want to validate?

    line 97
  5. Distinctive:

    The terminal state is invoking idea-intake: Do NOT invoke any research skill directly from brainstorming.

    line 105

“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “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

Business Idea Brainstorming

Overview

Help the user turn a raw business idea into a refined concept through natural collaborative dialogue. Explore the idea from multiple angles, challenge assumptions, and refine the value proposition before moving to structured intake.

<HARD-GATE> This skill MUST run before idea-intake. Do NOT skip brainstorming regardless of how clear the idea seems. Even "obvious" ideas have unexamined assumptions that waste research effort downstream. </HARD-GATE>

Process

digraph brainstorming {
    "Understand the raw idea" [shape=box];
    "Explore the problem space" [shape=box];
    "Explore target audience" [shape=box];
    "Explore business model options" [shape=box];
    "Propose 2-3 angles" [shape=box];
    "User picks direction" [shape=diamond];
    "Summarize refined concept" [shape=box, style=filled, fillcolor="#e8f5e9"];
    "Invoke idea-intake" [shape=doublecircle];

    "Understand the raw idea" -> "Explore the problem space";
    "Explore the problem space" -> "Explore target audience";
    "Explore target audience" -> "Explore business model options";
    "Explore business model options" -> "Propose 2-3 angles";
    "Propose 2-3 angles" -> "User picks direction";
    "User picks direction" -> "Propose 2-3 angles" [label="none fit"];
    "User picks direction" -> "Summarize refined concept" [label="chosen"];
    "Summarize refined concept" -> "Invoke idea-intake";
}

The Process

Ask questions one at a time via AskUserQuestion. Prefer multiple-choice where possible.

Phase 1: Understand the Raw Idea

Start with one open-ended question:

  • "Tell me your business idea in a few sentences — what is it and why does it matter?"

Listen. Don't jump to structure yet.

Phase 2: Explore the Problem Space

One question at a time:

  • Is this a problem you've experienced personally?
  • How are people solving this problem today? (Options: Manual workaround, Existing tools that don't fit well, They don't — they just live with it, Other)
  • How painful is this problem? (Options: Mild inconvenience, Significant frustration, Costs real money/time, Mission-critical blocker)
  • What triggers the moment someone realizes they need a solution?

Phase 3: Explore Target Audience

  • Who has this problem the most? (Options: Individuals/consumers, Small businesses, Mid-market companies, Enterprises, Specific profession/role, Other)
  • Can you describe your ideal first 10 customers?
  • How do these people currently find solutions? (Options: Google search, Word of mouth, Industry publications, They don't look — they've given up, Other)

Phase 4: Explore Business Model Options

Based on what you've learned, propose 2-3 realistic business model options:

  • Present each with one sentence explaining why it fits
  • Include trade-offs (e.g. "Subscription gives recurring revenue but requires continuous value delivery")
  • Ask which resonates most

Phase 5: Propose 2-3 Angles

Synthesize everything into 2-3 concrete product/positioning angles. For each angle:

  • One-liner: What it is in one sentence
  • Key bet: The main assumption that must be true
  • Advantage: Why this angle could win
  • Risk: The biggest concern

Present all angles and ask the user to pick one (or combine elements).

Phase 6: Summarize Refined Concept

Present a short summary of the refined idea:

## Refined Business Concept

**Idea:** [one sentence]
**Problem:** [what it solves]
**For:** [who]
**How it makes money:** [model]
**Key bet:** [the assumption that must hold]
**Unique angle:** [what makes this different]

Ask: "Does this capture what we want to validate? Anything to adjust before we start the formal intake?"

After Brainstorming

Once the user confirms the refined concept:

  1. Invoke business-validator:idea-intake to begin structured data collection
  2. The refined concept gives idea-intake a head start — many questions will already be partially answered

The terminal state is invoking idea-intake. Do NOT invoke any research skill directly from brainstorming.

Key Principles

  • One question at a time — don't overwhelm
  • Multiple choice preferred — faster for the user
  • Challenge assumptions — "why do you think X?" is a valid question
  • Stay curious, not critical — the goal is to refine, not to judge
  • No research yet — this is pure dialogue, no WebSearch
  • Keep it to 5-10 minutes — enough to refine, not so much that it delays the pipeline

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.