---
name: Symfony Brainstorming
slug: symfony-brainstorming
category: AI Engineering
description: Symfony Brainstorming helps plan medium-complex Symfony changes by clarifying constraints, proposing small architectural adjustments, and validating each checkpoint. Use it to structure collaborative design work and keep decisions auditable.
github: "https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/brainstorming"
language: TypeScript
stars: 208
forks: 20
install: "npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/brainstorming ~/.claude/skills/brainstorming"
installs_to: ~/.claude/skills/brainstorming
source_path: skills/brainstorming/SKILL.md
collection_size: 23
category_size: 2970
collection_url: "https://dirskills.com/collections/dev-toolings/superpowers-symfony"
added: 2026-09-04T05:27:05.159Z
last_synced: 2026-09-04T05:27:05.159Z
canonical_url: "https://dirskills.com/skills/symfony-brainstorming"
---

# Symfony Brainstorming

Symfony Brainstorming helps plan medium-complex Symfony changes by clarifying constraints, proposing small architectural adjustments, and validating each checkpoint. Use it to structure collaborative design work and keep decisions auditable.

**Install:**

```bash
npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/brainstorming ~/.claude/skills/brainstorming
```

## README

# 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`