phx-brainstorm

Gathers Elixir/Phoenix feature requirements through adaptive interviews and research into structured interview.md artifacts.

537|38|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-brainstorm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phx-brainstorm
Source: https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-brainstorm
Command: npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Vague feature ideas in Elixir/Phoenix projects often lead to poorly scoped plans and rework. This Skill turns an unclear idea into a structured, coverage-scored requirements document through guided interviewing and targeted research, so downstream planning starts with concrete context instead of guesswork.

Core Features & Use Cases

  • Adaptive Interview: Asks one question at a time across six coverage dimensions (What, Why, Scope, Where, How, Edge), scanning the codebase between questions to ground each question in real code.
  • Research Cycles: Spawns up to two background agents (codebase patterns analyst and web researcher) to compare approaches with thesis/antithesis trade-off analysis.
  • Structured Artifacts: Writes interview.md and research files to .claude/plans/{slug}/ that the phx-plan workflow consumes directly, skipping redundant clarification.
  • Use Case: You type a vague request like "add some kind of notification system" and the Skill interviews you about scope, edge cases, and constraints, researches Phoenix notification patterns, then hands a complete requirements document to the planning step.

Quick Start

Ask the AI to run the phx-brainstorm skill with your feature idea, for example to brainstorm improving authentication security in your Phoenix app.

Frequently Asked Questions about phx-brainstorm

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

FAQPage Schema
How do I brainstorm a new Phoenix feature before planning it?

Invoke phx-brainstorm with your topic, such as a notification system or authentication improvement. It interviews you one question at a time, scans your codebase for context, and writes a structured interview.md that the phx-plan workflow consumes directly.

How does the interview decide when enough requirements are gathered?

It scores six dimensions (What, Why, Scope, Where, How, Edge) from 0 to 2 each. The interview is considered sufficient when the total reaches 8 out of 12, and it stops asking about dimensions already fully covered.

Does phx-brainstorm research external Elixir libraries and patterns?

Yes. When you choose Research at a decision point, it spawns up to two background agents: one analyzes your codebase patterns and one researches community approaches and Hex packages, then presents 2-3 approaches with honest trade-offs.

Can I stop a brainstorm session and resume it later?

Yes. Choosing Store & exit saves all artifacts to .claude/plans/{slug}/ with status IN_PROGRESS. You can return in a later session and continue, or hand the saved interview.md to phx-plan when ready.

When should I skip brainstorming and go straight to planning?

Skip it when your requirements are already concrete with clear scope, constraints, and edge cases. Brainstorming adds the most value for vague ideas, niche topics needing research, or features with multiple viable architectural approaches.