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.