Brainstorm

Brainstorm

Invoke as $brainstorm.

Evaluate the current codebase and generate actionable suggestions that the user can take into $feature-interview for human/agent alignment, planning-destination triage, and follow-up specification or roadmap work.

Workflow

0. App Scope Resolution (Monorepo Support)

Before checking prerequisites, determine the app scope:

1. If $ARGUMENTS specifies an app name matching a subdirectory of research/, use it.
2. If research/ contains subdirectories (excluding files), list them and ask the user which app to target. If the session is already in Plan mode and there are 2-3 concrete choices, prefer request_user_input; otherwise ask in plain text. If only one subdirectory exists, use it automatically.
3. If no subdirectories exist, proceed with flat structure (single-product mode).

When app scope {app} is active:

• Read/write research from research/{app}/ instead of research/
• Read/write specs from specs/{app}/ instead of specs/
• Also read research/icp.md (cross-app overview) for broader context

1. Read CLAUDE.md, README, package config, and key source files to understand the project.

2. Check tasks/roadmap.md, tasks/todo.md, tasks/manual-todo.md, tasks/record-todo.md, tasks/recurring-todo.md (when they exist), and specs from specs/ (or spec.md) if they exist — avoid suggesting things already planned or deferred as advisory records. Read research/competitive-analysis.md (or research/{app}/competitive-analysis.md) if it exists — competitor gaps, market white space, and positioning weaknesses are high-signal inputs for ideation. Read research/customer-feedback.md (or research/{app}/customer-feedback.md) if it exists — "Wrong" and "New" findings are highest-signal ideation input. Read research/metrics.md (or research/{app}/metrics.md) if it exists — instrumentation gaps can generate ideas.

3. Analyse the codebase across these dimensions:

   Strategic / Product

   • New features that would make the project significantly more useful or valuable
   • New workflows or end-to-end automation the project could enable
   • Product line expansion — adjacent use cases, new audiences, or complementary products the core could serve
   • Integration opportunities with external tools, platforms, or APIs that multiply value

   Improvement

   • Missing capabilities the architecture is set up for
   • Pain points, rough edges, or manual steps that could be automated
   • Performance bottlenecks or low-hanging optimisations
   • Developer experience friction

   Hygiene

   • Technical debt where code has outgrown its design
   • Testing gaps in critical paths
   • Security hardening opportunities

   Market Fit (only when research/icp.md (or research/{app}/icp.md), research/mvp-gap.md (or research/{app}/mvp-gap.md), or research/competitive-analysis.md (or research/{app}/competitive-analysis.md) exist)

   • ICP alignment — features addressing ICP pain points that are missing or incomplete
   • Journey gaps — steps where the product loses the user or customer
   • Unaddressed MVP gaps from research/mvp-gap.md (or research/{app}/mvp-gap.md) not yet in roadmap
   • Competitive white space — features or capabilities no competitor offers well, from research/competitive-analysis.md (or research/{app}/competitive-analysis.md) market gaps
   • Competitor leapfrog — specific competitor weaknesses to exploit, or table-stakes features competitors have that you lack
   • Positioning plays — ideas that sharpen differentiation against the competitive landscape

4. If the user provides a focus area, scope the analysis there. Otherwise cover all dimensions.

Output

Append the suggestions to tasks/ideas.md (do not overwrite existing content). Also display them to the user. When app scope is active, prefix each suggestion with the app name.

Group suggestions by effort level (hours / days / weeks). Each suggestion should include:

• A specific, actionable title
• A one-line description with the concrete codebase signal that motivates it
• A $feature-interview <topic> prompt the user can copy-paste

Constraints

• Be specific and actionable — no vague aspirations.
• Limit to 3–5 suggestions per effort level.
• Do not suggest changes that conflict with CLAUDE.md conventions.
• Do not repeat work already in tasks/roadmap.md, tasks/todo.md, tasks/manual-todo.md, tasks/record-todo.md, tasks/recurring-todo.md, or specs/ (or specs/{app}/).

Alignment Page

When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following ALIGNMENT-PAGE.md in this skill's directory. Output: alignment/brainstorm-{topic}.html.

Default Shipping Contract

Follow the shared shipping contract convention in CLAUDE.md.