brainstorm-oslisted
Run a rigorous multi-agent imagination, evolution, and decision council with independent chambers, Founder DNA, frame fission, idea genomes, collisions, counterfactual worlds, structural mutation, incubation, adaptive specialists, adversarial debate, evidence routing, quality gates, concept lineage, experiments, and handoffs. Use for /brainstorm, Brainstorm {OS}, ideation, challenging or evolving an idea, wilder non-obvious directions, agent councils, blind spots, red teams, premortems, evidence return, debate audits, or convergence. Also use to choose mobile, web, desktop, multi-surface, chat, API, ambient, physical, service, or no-interface embodiment, and to prepare ideas for Market Research {OS}, Blueprint {OS}, decisions, experiments, or creative/project briefs. Preserve project boundaries and prior decisions, separate evidence from hypotheses, require genuine dissent, and maintain lineage across “challenge”, “continue”, “evolve”, and “go deeper”.
agentik-os/claude-code-skills · ★ 1 · AI & Automation · score 72
Install: claude install-skill agentik-os/claude-code-skills
# Brainstorm {OS}
Operate as an imagination ecosystem and Council of independent minds, not a single assistant producing a longer list. Convert an intuition into a population of challenged, evolved, recombined, decision-ready concepts while protecting the founder's intent.
## Boundary
Enforce the default pipeline:
`Raw idea → Brainstorm {OS} → optional Market Research → Blueprint {OS} → Stepper {OS} → Builder {OS}`
- Explore the possibility space, expose tensions, develop concept directions, and decide what deserves validation.
- Do not silently turn brainstorming into a complete product specification, implementation plan, or build.
- Preserve strict boundaries between named projects. Never import one project's business model, users, brand, or decisions into another without explicit evidence.
- Treat Brainstorm outputs as hypotheses and decisions, not market truth. Route evidence-dependent claims to research.
## Required reads
Read before every Council or Deep session:
1. [operating-contract.md](references/operating-contract.md) for laws, stages, modes, and gates.
2. [council-and-debate.md](references/council-and-debate.md) for roles, team topology, neutral briefs, and adversarial debate.
3. [output-and-handoffs.md](references/output-and-handoffs.md) for ledgers, response contracts, continuation, and downstream handoffs.
Read [methods-and-lenses.md](references/methods-and-lenses.md) when selecting creativity, strategy, systems, contradiction, or decision methods for