brainstorming · dev-toolings — Claude Code skill: what it does, how to install
brainstorming structures feature discovery for Symfony projects: clarifies unclear requirements, identifies framework components, and compares architecture designs.
MIT ★ 234 updated 2026-10-05
npx skills add dev-toolings/superpowers-symfony --skill brainstorming -a claude-codeWhat brainstorming does
This skill guides architecture discussions before drafting implementation steps or writing code. It reframes feature objectives, highlights boundaries, and prompts for missing details regarding user roles, permissions, data models, and error paths.
The workflow maps requirements directly to Symfony primitives, such as entities, service handlers, API resources, security voters, and async messenger transports. It evaluates two or three architectural approaches alongside their tradeoffs, with instructions to favor conventions already present in the codebase. Project inspection relies strictly on read-only tools: Read, Glob, and Grep.
Implementation stops at design selection: the skill forbids code authoring and hands off the chosen approach and noted risks to writing-plans.
What it helps with
- clarify vague feature requirements before writing code
- identify relevant Symfony components for a new module
- compare multiple architectural options and evaluate tradeoffs
- document rejected approaches and open technical risks
Example prompts for the agent
- Let's brainstorm the checkout workflow for our Symfony store before writing any plan
- Map out the required Symfony entities, voters, and async messages for background report generation
- Explore architectural options to implement multi-tenant authentication using our existing patterns
How to install brainstorming
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill brainstorming -a claude-code2Manually: put the files in place
~/.claude/skills/brainstorming/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/brainstorming/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill brainstorming -a codex2Manually: put the files in place
.agents/skills/brainstorming/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill brainstorming -a cursor2Manually: put the files in place
.cursor/skills/brainstorming/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dev-toolings/superpowers-symfony content/skills/brainstorming2Manually: put the files in place
.github/skills/brainstorming/SKILL.md1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill brainstorming -a gemini-cli2Platform CLI
gemini skills install https://github.com/dev-toolings/superpowers-symfony --path content/skills/brainstormingManually: put the files in place
.devin/skills/brainstorming/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about brainstorming
How to install brainstorming in Claude Code?
Run npx skills add dev-toolings/superpowers-symfony --skill brainstorming -a claude-code. Alternatively, copy the skill definition file to ~/.claude/skills/brainstorming/SKILL.md.
What does brainstorming do?
It facilitates architectural discussions for Symfony applications, helping you explore requirements, select framework components, and compare design choices before planning work.
Does brainstorming generate project code?
No, the skill rules explicitly forbid writing code or step-by-step implementation plans, handing off the chosen design to writing-plans.
Source text
SKILL.md · MIT
--- name: brainstorming description: Structured brainstorming for Symfony projects - explore requirements, identify components, and plan architecture collaboratively capabilities: [read, search] tags: [workflow] # projected by `bun run build` — do not edit by hand allowed-tools: - Read - Glob - Grep --- # Brainstorming (Symfony) ## Use when - A feature request is still vague and the requirements are not settled. - Several designs are possible and the tradeoffs must be compared before choosing. - You need to know which Symfony components a feature touches (entities, handlers, API resources, security, async) before planning. - The decision must be made before a plan is written; once it is, hand off to `writing-plans`. ## Default workflow 1. Restate the goal in one sentence and list what is known, unknown and out of scope. 2. Ask the open questions (users, data, permissions, failure cases) and note the answers. 3. Map the feature onto Symfony components: entities, services and handlers, API resources, voters, messages. 4. Propose two or three designs with their tradeoffs and recommend one. 5. Record the chosen design, the rejected options and the open risks, then hand off to `writing-plans`. ## Guardrails - Do not write code or a step-by-step plan here: brainstorming ends at a chosen design. - Prefer the patterns already present in the project over new ones. - Ask one question at a time instead of guessing a missing requirement. - Keep rejected options in the notes so the decision stays auditable. ## Progressive disclosure - Use this file for execution posture and risk controls. - Open references when deep implementation details are needed. ## Output contract - The goal, scope and answered questions. - The components involved and the recommended design with its tradeoffs. - Open risks, ready to feed `writing-plans`. ## References
© dev-toolings · MIT · dev-toolings/superpowers-symfony
Similar skills
All skills for Backend and APIs →brainstorming by other authors comes first.