orc-brainstorm

Generates and stress-tests idea candidates through structured diverge-converge brainstorming phases.

6|1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/azure-id/orc --skill orc-brainstorm-azure-id
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orc-brainstorm
Source: https://github.com/azure-id/orc/tree/main/templates/skills/orc-brainstorm
Command: npx skills add https://github.com/azure-id/orc --skill orc-brainstorm-azure-id

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When facing an open problem — a product decision, an onboarding flow, a naming question, or a technical direction — teams often jump on the first idea instead of the best one. This Skill runs a disciplined brainstorming session that deliberately generates many options, clusters them into real directions, stress-tests each, and records why every rejected idea lost. ## Core Features & Use Cases - Structured divergence: Generates at least 8 candidates across at least 3 named thinking lenses (SCAMPER, inversion, Six Thinking Hats, analogy, constraint-flip, first-principles, repo precedent) with critique switched off during generation. - Converge without deciding for you: Clusters candidates into 3-5 directions, pre-mortems each one, states a recommendation, then waits — the user always makes the final pick, and every menu includes an open slot for the user's own idea. - Persistent session document: Writes a brainstorm-session.md capturing the problem, all candidates, directions, the pick, and the reasons every loser lost, so future sessions never re-propose dead ideas. - Use Case: Ask "how should we onboard new merchants?" and receive a framed problem statement, a dozen lens-generated candidates, four stress-tested directions, and a written record of the chosen direction with tagged constraints ready to hand off to analysis or planning lanes. ## Quick Start Ask the assistant to run /orc-brainstorm on a problem like "our support queue is drowning us" and let it generate and stress-test options before you pick one.

Frequently Asked Questions about orc-brainstorm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I brainstorm product or feature ideas with an AI assistant?▼

Invoke /orc-brainstorm with your problem statement. It frames the problem, generates at least 8 candidates across 3 or more thinking lenses, clusters them into directions, stress-tests each, and waits for you to pick before writing anything down.

What thinking lenses does the brainstorm lane use to generate ideas?▼

It uses a catalogue of seven lenses: SCAMPER, inversion, Six Thinking Hats, analogy and precedent, constraint-flip, first principles, and this-repo precedent for code topics. Each batch of candidates announces the lens used so you can request a different one.

Can I use orc-brainstorm for non-code problems like naming or onboarding flows?▼

Yes. The lane explicitly supports non-code topics such as product names, onboarding flows, and support-queue problems. On non-code topics it skips repository knowledge probes and the code-analysis handoff, printing the reason instead.

Does the brainstorm skill decide which idea is best for me?▼

No. It states a recommendation and argues for it, but never picks for you. Every menu includes an open slot for your own idea, which is stress-tested identically to the generated candidates, and the session document is only written after your explicit yes.

What is the difference between orc-brainstorm and orc-grill?▼

Brainstorm diverges first to generate options when you do not yet have an idea; grill converges on one idea you already have by asking questions. They compose: brainstorm picks the mountain, grill picks the path up it, and each can hand off to the other mid-run.

Where does orc-brainstorm save the session results?▼

It writes a brainstorm-session.md under orc/brainstorming-session/<slug>/ at the project root, never inside .claude/. The file records the problem, all candidates, directions, the pick, and why every rejected option lost, and re-opening a topic extends the same file.