writing-plans_skill

Overview

This skill helps produce focused, production-grade Symfony architecture and execution plans with controlled scope and clear checkpoints. It is designed for teams that need safe, incremental changes to architecture or workflows while keeping risk auditable and reversible. The outputs are concrete adjustments, validation checkpoints, and a follow-up backlog.

How this skill works

I inspect the current boundaries, constraints, and coupling points in your Symfony project and propose the smallest coherent architectural adjustment that meets your goal. Plans are broken into checkpoints with explicit validation criteria and rollback paths. Each checkpoint includes tradeoff notes, residual risks, and next steps to keep decisions auditable.

When to use it

• Refining execution workflows or context handling in a Symfony application
• Planning medium-to-complex changes that must be delivered safely
• Introducing a new service boundary, integration, or data flow
• When you need checkpointed delivery with built-in validation and rollback
• Auditing or documenting architectural decisions for compliance or onboarding

Best practices

• Default to existing project patterns and conventions to minimize risk
• Propose the smallest coherent change that accomplishes the goal
• Break work into checkpoints with clear validation and rollback criteria
• Keep a concise decision log recording tradeoffs and reasons
• Avoid broad refactors unless explicitly justified by metrics or risk

Example use cases

• Add a new bounded context façade to decouple a legacy domain service
• Introduce a background worker and messaging flow with staged rollout
• Migrate a portion of authentication to a token-based gateway with tests
• Refine request context propagation across middleware and event listeners
• Plan a database migration with backward-compatible schema and checkpoints