Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/dev-toolings/superpowers-symfony --skill executing-plansAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
Executing Plans (Symfony)
Use when
- An approved implementation plan exists and must be carried out.
- The work spans several steps that must each land green.
- Resuming a plan after an interruption or a blocker.
Default workflow
- Read the whole plan, confirm the baseline tests pass, and work on a branch.
- For each step, write the test, watch it fail, implement, watch it pass, then refactor.
- Commit after each completed step, with a message that names it.
- Run the quality gates (style, static analysis, full suite) at the end of each phase.
- Track each step's status in the plan, and stop to report when reality contradicts it.
Guardrails
- Never skip watching the test fail: a test that never failed proves nothing.
- One step per commit; do not batch steps.
- Do not change the plan silently: report the deviation and the reason.
- On a blocker (failing migration, autowiring error), fix the cause, not the test.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- One commit per step, tests included.
- The plan with the status of every step.
- Final validation results and any deviation from the plan.
References
reference.md
