brainstorm-with-file_skill

Overview

This skill enables interactive, documented brainstorming driven by a file-backed workflow and parallel subagent collaboration. It expands a seed idea through progressive questioning, concurrent multi-perspective analysis, and iterative refinement, producing a complete thought-evolution timeline and structured artifacts. The workflow is optimized for Codex-style agents and JSON-driven orchestration.

How this skill works

The workflow parses a seed idea, generates exploration vectors, and gathers codebase context. It then spawns parallel subagents (creative, pragmatic, systematic) to explore perspectives concurrently, aggregates their outputs, and runs iterative refinement cycles using multi-round agent inputs. Final synthesis and idea deep-dives are written to a session folder with a documented brainstorm.md timeline and related JSON artifacts.

When to use it

• When you need fast, multi-perspective exploration of a technical idea tied to a codebase.
• When you want a documented history of idea evolution and decision rationale.
• When parallel analysis (creative vs pragmatic vs systematic) surfaces better options.
• When you need Codex-compatible agent orchestration with lifecycle control.
• When you want structured outputs for follow-up engineering or product planning.

Best practices

• Start each session with a clear seed idea and chosen brainstorm mode (creative, balanced, structured).
• Let the workflow auto-detect project root to ensure artifacts land in .workflow/.brainstorm session folder.
• Use exploration vectors to steer each perspective agent and keep tasks focused and measurable.
• Spawn parallel agents, batch-wait for results, then synthesize—preserve each agent’s output for auditability.
• Iterate via send_input within agents for multi-round refinement instead of spawning new agents for small follow-ups.

Example use cases

• Evaluate multiple implementation approaches for a new feature while preserving the decision timeline.
• Run rapid innovation sprints that contrast moonshot ideas with pragmatic trade-offs and architecture constraints.
• Audit legacy code to find viable integration strategies and record findings in exploration-codebase.json.
• Produce prioritized recommendations and implementation plans with documented reasoning in synthesis.json.
• Generate and refine multiple candidate designs, each saved as an ideas/{idea-slug}.md deep dive.