symfony:executing-plans
Executing Plans (Symfony)
Use when
- Refining architecture/workflows/context handling in Symfony projects.
- Planning and executing medium/complex changes safely.
Default workflow
- Establish current boundaries, constraints, and coupling points.
- Propose smallest coherent architectural adjustment.
- Execute in checkpoints with validation at each stage.
- 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
reference.mddocs/complexity-tiers.md
More from makfly/superpowers-symfony
symfony:interfaces-and-autowiring
Apply production-grade Symfony architecture and execution workflows with controlled scope and clear checkpoints. Use for interfaces and autowiring tasks.
377symfony:controller-cleanup
Apply production-grade Symfony architecture and execution workflows with controlled scope and clear checkpoints. Use for controller cleanup tasks.
344symfony:twig-components
Apply production-grade Symfony architecture and execution workflows with controlled scope and clear checkpoints. Use for twig components tasks.
315symfony:using-symfony-superpowers
Apply production-grade Symfony architecture and execution workflows with controlled scope and clear checkpoints. Use for using symfony superpowers tasks.
304symfony:effective-context
Apply production-grade Symfony architecture and execution workflows with controlled scope and clear checkpoints. Use for effective context tasks.
303symfony:symfony-messenger
Implement resilient Symfony async workflows with idempotency, retries, and operational visibility. Use for symfony messenger tasks.
301