Symfony:brainstorming Skill
- 420 installs
- 190 repo stars
- Updated August 6, 2026
- makfly/superpowers-symfony
symfony:brainstorming is a Symfony agent skill that explores feature directions, module boundaries, and technical options through structured ideation for developers who plan new endpoints, bundles, or refactors.
About
symfony:brainstorming is a read-only Symfony planning skill from makfly/superpowers-symfony, one of 44 Symfony skill definitions in that library. It guides collaborative exploration of requirements, component identification, and architecture planning before code changes. The default workflow establishes current boundaries, constraints, and coupling points; proposes the smallest coherent architectural adjustment; executes in checkpoints with validation at each stage; and summarizes tradeoffs plus a follow-up backlog. Guardrails enforce existing project patterns, avoid broad refactors without explicit need, and keep a clear auditable decision log. Allowed tools are Read, Glob, and Grep only—no writes during brainstorming. Developers reach for symfony:brainstorming when refining Symfony architecture, planning medium-to-complex changes safely, or deciding module boundaries for new API endpoints or bundle extractions.
- Domain-driven feature mapping
- Bundle and service boundary options
- Risk and dependency surfacing
- Symfony-pattern-aware ideation
- Decision prep for ADRs
Symfony:Brainstorming by the numbers
- 420 all-time installs (skills.sh)
- Ranked #805 of 3,347 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 11, 2026 (Skillselion catalog sync)
npx skills add https://github.com/makfly/superpowers-symfony --skill symfonybrainstormingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 420 |
|---|---|
| repo stars | ★ 190 |
| Last updated | August 6, 2026 |
| Repository | makfly/superpowers-symfony ↗ |
How do you plan Symfony architecture before coding?
Explore Symfony feature directions, module boundaries, and technical options before committing to architecture—structured ideation for new endpoints, bundles, or refactors.
Who is it for?
Symfony developers planning new endpoints, bundle splits, or medium-complex refactors who need structured ideation before touching code.
Skip if: Greenfield projects without an existing Symfony codebase or developers who already have a finalized implementation plan ready to code.
When should I use this skill?
The developer asks to brainstorm Symfony features, explore module boundaries, plan bundle architecture, or evaluate refactor options before implementation.
What you get
Architecture options, coupling analysis, checkpoint plan, tradeoff summary, and prioritized follow-up backlog
- Architecture options document
- Checkpoint plan
- Follow-up backlog
By the numbers
- Part of superpowers-symfony's 44 Symfony skill definitions
- Default workflow has 4 checkpoint stages
Files
Brainstorming (Symfony)
Use when
- Refining architecture/workflows/context handling in Symfony projects.
- Planning and executing medium/complex changes safely.
Default workflow
1. Establish current boundaries, constraints, and coupling points. 2. Propose smallest coherent architectural adjustment. 3. Execute in checkpoints with validation at each stage. 4. Summarize tradeoffs and follow-up backlog.
Guardrails
- Use existing project patterns by default.
- Avoid broad refactors without explicit need.
- Keep decision log clear and auditable.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- Architecture/workflow changes.
- Checkpoint validation outcomes.
- Residual risks and next steps.
References
docs/complexity-tiers.md
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.787k210kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.669k210k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.542kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.542kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).542kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.541kHow it compares
Pick symfony:brainstorming over implementation skills when Symfony architecture direction is still undecided and you need tradeoff analysis before coding.
FAQ
What tools does symfony:brainstorming allow?
symfony:brainstorming restricts agents to Read, Glob, and Grep. The read-only posture keeps brainstorming exploratory—mapping boundaries and coupling without modifying Symfony source files during ideation.
When should symfony:brainstorming run in a Symfony project?
symfony:brainstorming fits before medium or complex Symfony changes: new endpoints, bundle extractions, workflow refactors, or context-handling adjustments. Run it when architecture direction is unclear and coupling risks need mapping first.