Symfony:runner Selection Skill
- 392 installs
- 190 repo stars
- Updated August 6, 2026
- makfly/superpowers-symfony
symfony:runner-selection is an agent skill that chooses the correct Symfony command runner across Docker Compose, FrankenPHP, or host environments for developers implementing tests, console commands, or CI jobs.
About
symfony:runner-selection is a makfly/superpowers-symfony skill that selects and configures the appropriate command execution environment for Symfony projects. It detects three runner contexts—standard Docker Compose, Symfony Docker with FrankenPHP, and bare host execution—and applies production-grade architecture workflows with controlled scope and validation checkpoints. The skill inspects current boundaries, coupling points, and context-handling patterns to propose the smallest coherent change, logging decisions and rollback points along the way. Use it when running PHPUnit or Pest tests, Symfony console commands, Messenger workers, or CI jobs where the wrong runner causes missing services or context propagation failures. Developers reach for symfony:runner-selection before medium or complex Symfony changes that affect where commands execute.
- Maps Symfony tasks to appropriate runners
- Covers test, console, Messenger, and CI contexts
- Prevents runner mismatch during agent-driven changes
- Aligns automation with Symfony execution models
- Speeds backend workflow decisions
Symfony:Runner Selection by the numbers
- 392 all-time installs (skills.sh)
- Ranked #25 of 68 PHP & Laravel skills by installs in the Skillselion catalog
- Data as of Aug 11, 2026 (Skillselion catalog sync)
npx skills add https://github.com/makfly/superpowers-symfony --skill symfonyrunner-selectionAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 392 |
|---|---|
| repo stars | ★ 190 |
| Last updated | August 6, 2026 |
| Repository | makfly/superpowers-symfony ↗ |
How do you pick the right Symfony command runner?
Choose the right Symfony execution runner for tests, console commands, Messenger workers, or CI jobs before implementing or debugging backend work.
Who is it for?
Symfony developers working across Docker Compose, FrankenPHP, and host environments who need reliable test, console, and worker execution setup.
Skip if: Non-Symfony projects or simple single-environment setups where the runner is already documented and never changes.
When should I use this skill?
User asks how to run Symfony tests or console commands, mentions Docker vs host execution, Messenger workers, or CI runner selection in Symfony.
What you get
Selected runner configuration, validation checkpoints, decision record, and rollback plan for Symfony command execution.
- runner configuration
- decision record
- validation checkpoints
By the numbers
- Detects 3 execution contexts: Docker Compose, Symfony Docker FrankenPHP, and host
Files
Brainstorming (Symfony)
Use when
- Refining architecture/workflows/context handling in Symfony projects.
- Planning and executing medium/complex changes safely.
Default workflow
1. Establish current boundaries, constraints, and coupling points. 2. Propose smallest coherent architectural adjustment. 3. Execute in checkpoints with validation at each stage. 4. 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
docs/complexity-tiers.md
Related skills
Laravel SpecialistGenerate correct, idiomatic Laravel Eloquent models, relationships, accessors, and query patterns using an agent.19.9k11kPhp ProGenerate production-grade async PHP patterns using Swoole for high-performance HTTP servers and concurrent operations.13.1k11k
Laravel TddFollow strict red-green-refactor cycles while building Laravel features with PHPUnit or Pest at 80%+ coverage.5.9k239k
Wp Plugin DevelopmentGet an agent that knows WordPress plugin architecture, hooks, security rules, and packaging workflows.5.1k2kLaravel VerificationRun a complete verification loop on Laravel projects before opening PRs or deploying.4.8k239kWordpress RouterInstantly classify any WordPress codebase and hand off to the correct specialized workflow.3.5k2kHow it compares
Pick symfony:runner-selection for execution environment detection; use symfony:bootstrap-check when verifying initial Symfony project configuration instead.
FAQ
Which environments does symfony:runner-selection detect?
symfony:runner-selection detects standard Docker Compose setups, Symfony Docker with FrankenPHP, and bare host execution, then configures commands and tests for the matching runner.
What Symfony tasks does symfony:runner-selection cover?
symfony:runner-selection covers PHPUnit or Pest tests, Symfony console commands, Messenger workers, and CI job execution where the wrong runner breaks service or context propagation.
How does symfony:runner-selection reduce risk?
symfony:runner-selection executes changes in discrete checkpoints with validation criteria, logs decision rationale, and documents rollback points before altering execution boundaries.