brainstorming

Files (200)

• SKILL.md
• builder-check-prompt.md
• frame-template.html · scripts/
• helper.js · scripts/
• index.js · scripts/
• mime · scripts/node_modules/.bin/
• .package-lock.json · scripts/node_modules/
• HISTORY.md · scripts/node_modules/accepts/
• LICENSE · scripts/node_modules/accepts/
• README.md · scripts/node_modules/accepts/
• index.js · scripts/node_modules/accepts/
• package.json · scripts/node_modules/accepts/
• LICENSE · scripts/node_modules/anymatch/
• README.md · scripts/node_modules/anymatch/
• index.d.ts · scripts/node_modules/anymatch/
• index.js · scripts/node_modules/anymatch/
• package.json · scripts/node_modules/anymatch/
• LICENSE · scripts/node_modules/array-flatten/
• README.md · scripts/node_modules/array-flatten/
• array-flatten.js · scripts/node_modules/array-flatten/
• package.json · scripts/node_modules/array-flatten/
• binary-extensions.json · scripts/node_modules/binary-extensions/
• binary-extensions.json.d.ts · scripts/node_modules/binary-extensions/
• index.d.ts · scripts/node_modules/binary-extensions/
• index.js · scripts/node_modules/binary-extensions/
• license · scripts/node_modules/binary-extensions/
• package.json · scripts/node_modules/binary-extensions/
• readme.md · scripts/node_modules/binary-extensions/
• HISTORY.md · scripts/node_modules/body-parser/
• LICENSE · scripts/node_modules/body-parser/
• README.md · scripts/node_modules/body-parser/
• index.js · scripts/node_modules/body-parser/
• read.js · scripts/node_modules/body-parser/lib/
• json.js · scripts/node_modules/body-parser/lib/types/
• raw.js · scripts/node_modules/body-parser/lib/types/
• text.js · scripts/node_modules/body-parser/lib/types/
• urlencoded.js · scripts/node_modules/body-parser/lib/types/
• package.json · scripts/node_modules/body-parser/
• LICENSE · scripts/node_modules/braces/
• README.md · scripts/node_modules/braces/
• index.js · scripts/node_modules/braces/
• compile.js · scripts/node_modules/braces/lib/
• constants.js · scripts/node_modules/braces/lib/
• expand.js · scripts/node_modules/braces/lib/
• parse.js · scripts/node_modules/braces/lib/
• stringify.js · scripts/node_modules/braces/lib/
• utils.js · scripts/node_modules/braces/lib/
• package.json · scripts/node_modules/braces/
• History.md · scripts/node_modules/bytes/
• LICENSE · scripts/node_modules/bytes/
• Readme.md · scripts/node_modules/bytes/
• index.js · scripts/node_modules/bytes/
• package.json · scripts/node_modules/bytes/
• .eslintrc · scripts/node_modules/call-bind-apply-helpers/
• FUNDING.yml · scripts/node_modules/call-bind-apply-helpers/.github/
• .nycrc · scripts/node_modules/call-bind-apply-helpers/
• CHANGELOG.md · scripts/node_modules/call-bind-apply-helpers/
• LICENSE · scripts/node_modules/call-bind-apply-helpers/
• README.md · scripts/node_modules/call-bind-apply-helpers/
• actualApply.d.ts · scripts/node_modules/call-bind-apply-helpers/
• …and 140 more

SKILL.md (first lines)

# Brainstorming

You are very good at building. You build what you believe your human
partner wants, and that belief is usually thinner than it feels. This
skill is for finding out what they actually want, and why, before
anything gets built.

People often haven't finished working out what they want. Good questions
help them think it through. When you understand the why, you make the
hundred decisions they never mention the way they would have made them.

## First: What Do You Actually Know?

Before you reply, ask yourself: what do I know about what they want, and
why?

- **Everything that matters is in the request** ("make the icon cornflower
  blue"). This is a quick, clear task. Do it, and say what you did.
- **Something non-trivial is missing.** Start the conversation.

Before you start implementing, you must, in order:

1. Lay out the approaches in a message of their own, and have your
   human partner pick one (see Lay out the approaches).
2. Write the design doc, short or full (see Size the Work).
3. Get their approval of that doc.
4. Invoke the superpowers:writing-plans skill.

Two things aren't implementing: a spike they said yes to (see Spike to
feel things out), and doing what they asked once they've opted out of
the questions.

## Look Before You Ask

In an existing project, or when they've given you context (a spec, a plan,
a handoff, files they pointed at, earlier conversation), dig in before your
first message. Read what they referred to and the code or material it
connects to, and keep reading until you can explain how the relevant
parts work today and what this change would touch. Never ask what the
project or their context already answers.

## Your First Message

Move the work forward, with one of these:

- **They've already said what they want** (a spec, a plan, a detailed
  request): aim for about 200 words for the whole message. Echo their
  request back in your own words, so they can see whether you've got its
  shape: what they want, who it's for, and why, as far as they've said.
  Add what you found that bears on it: how the relevant parts work today
  and what the change would touch. If you found something they may not
  have considered that would change what they're asking for or how it
  has to be built, like a constraint, a conflict, or a cheaper path, say
  so plainly. How to build it comes later, once you understand what they
  want (see Lay out the approaches). End with one line inviting
  corrections, then one question about what they want: the thing their
  request leaves open whose answer would most change what gets built.
  Specs are often incomplete, so confirm before you build on one.
- **They haven't:** one open question, in their own terms, about the
  biggest thing their request leaves unsettled. Say why you're asking:
  what the answer would change about what you build. For "a website for
  my bakery": "If it's mostly for people deciding whether to stop by,
  I'd lead with hours and what's in the case today; taking orders is a
  different site. What do you want someone to do when they land on it?"

How the message ends depends on whether their message asked for
brainstorming:

- **They asked for it** (by name, by invoking it, or by asking for a
  design discussion): end with your question. They want this
  conversation.
- **They didn't:** they may not want a conversation at all. After your
  question, add a light, one-line offer to just get going instead, like
  "Or if you'd rather I just dive in, say so." If they take you up on
  it, this skill is done: state any significant how-it-gets-made choice
  (platform, language, medium) in one plain line, then do what they
  asked through the normal workflow.

That's the whole message.

## The Conversation

Each message ends with one question: a single sentence with no list of
example answers hanging off it. Use plain language, pitched just a little
above where your human partner is. Match their vocabulary; never use
process jargon. You never need to quote this skill to your human
partner.

Be clear and concise. Lead with what matters. Avoid jargon. When you
report what you found, give them the most important findings and offer
the rest.

**Get them describing.** Open questions come first. Their own words carry
intent that your options can't. Offer a short menu only when they're
stuck. When they say "just guess" or "what do you think?", propose
something concrete.

**How it gets made.** Every project rests on choices about medium, tools,
materials, and resources: the platform, programming language, and
libraries for an app; the medium for a piece of art. Find out early which
of those choices they want to make, which they're handing to you, and what
they already have to work with. Someone with strong views or skills will
want to talk it through. Someone counting on you needs sensible defaults,
said in plain words. When there's existing work, build on what it already
uses. Any choice you make goes in the design as your call, never as
something they agreed to.

**Ground to cover.** This is territory, not a script. Never read these
out as questions:

- what kind of thing this is, and what makes it special
- why now, and what success looks like to them
- goals, non-goals, and anti-goals (what would make this a failure even
  if it technically works)
- prior art: what they've seen elsewhere, loved or hated
- current state: what exists now, what they've tried
- the details they care about

**Make every question specific** to their project and what they've told

From guanyang/open-agent-hub, MIT.

More from guanyang/open-agent-hub