runner-selection_skill

Overview

This skill applies production-grade Symfony architecture and execution workflows with controlled scope and clear checkpoints. It focuses on runner selection tasks: choosing where and how a change executes within an application. The goal is safe, minimal-impact adjustments with auditable decisions and rollback points.

How this skill works

I inspect current boundaries, coupling points, and context-handling patterns to identify the smallest coherent architectural change that addresses the need. Changes are executed in discrete checkpoints; each checkpoint includes validation criteria and acceptance gates. At the end I produce a concise summary of tradeoffs, residual risks, and a follow-up backlog for next steps.

When to use it

• When planning medium or complex changes that affect execution scope or context propagation.
• When introducing new runners, command handlers, or process boundaries in a Symfony app.
• When you need auditable decisions and safe rollback points for architectural changes.
• When adopting third-party execution frameworks or changing where jobs run.

Best practices

• Prefer existing project patterns and conventions; avoid broad refactors by default.
• Define validation criteria for each checkpoint before executing code changes.
• Log decisions, alternatives considered, and reasoning in a simple decision record.
• Limit scope to the smallest change that maintains functional integrity.
• Document residual risks and schedule follow-up work items for deferred concerns.

Example use cases

• Selecting a runner for background tasks while preserving request-context behavior.
• Migrating a set of command handlers to a new execution boundary with staged rollout.
• Adding a new runner for high-priority jobs and validating integrity across checkpoints.
• Adjusting context propagation for a microservice call chain and auditing the change.