Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
makfly avatar

Symfony:symfony Scheduler Skill

  • 389 installs
  • 190 repo stars
  • Updated August 6, 2026
  • makfly/superpowers-symfony

symfony:symfony-scheduler is an agent skill that configures Symfony Scheduler recurring tasks and Messenger-backed async handlers for developers who need cron-like PHP background work without manual crontab wiring.

About

symfony:symfony-scheduler is a Symfony-focused agent skill from makfly/superpowers-symfony for defining recurring jobs with the Scheduler component native since Symfony 7.x. The workflow walks through async contracts, idempotent Messenger handlers, routing, retry policies, failure transports, and poison-message handling with at-least-once delivery assumptions. Developers reach for symfony:symfony-scheduler when replacing fragile server crontab entries with in-app schedules, stabilizing background retries, or integrating observability around async PHP workloads. Output includes updated async configuration, handler code, retry and failure policy decisions, and operational validation notes. The skill references companion docs for complexity tiers and deep implementation patterns when progressive disclosure is needed.

  • Symfony Scheduler
  • recurring jobs
  • cron replacement
  • PHP backend
  • task triggers

Symfony:Symfony Scheduler by the numbers

  • 389 all-time installs (skills.sh)
  • Ranked #26 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 symfonysymfony-scheduler

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs389
repo stars190
Last updatedAugust 6, 2026
Repositorymakfly/superpowers-symfony

How do you schedule recurring Symfony jobs without crontab?

Configure Symfony Scheduler for recurring jobs, cron-like tasks, and background work in PHP apps without manual crontab wiring.

Who is it for?

PHP backend engineers shipping Symfony 7.x APIs or SaaS apps that need reliable recurring background work integrated with Messenger.

Skip if: Teams on pre-7 Symfony versions without Scheduler, pure frontend work, or infrastructure that only needs OS-level cron with no PHP integration.

When should I use this skill?

User asks to add Symfony Scheduler, recurring Messenger tasks, cron replacement, retry policies, or failure transports in a Symfony PHP app.

What you get

Async Scheduler and Messenger configuration, idempotent handler implementations, retry and failure-transport policy, and operational validation evidence.

  • Scheduler and Messenger configuration
  • Idempotent handler code
  • Retry and failure-transport policy notes

By the numbers

  • Targets Symfony Scheduler native since Symfony 7.x
  • Four-step default workflow from contract definition through operational validation

Files

SKILL.mdMarkdownGitHub ↗

Symfony Scheduler (Symfony)

Use when

  • Implementing asynchronous workflows with Messenger/Scheduler/Cache.
  • Stabilizing retries and failure transports.

Default workflow

1. Define async contract and delivery semantics. 2. Implement idempotent handlers and routing strategy. 3. Configure retries, failure transport, and observability. 4. Validate success/failure replay scenarios.

Guardrails

  • Assume at-least-once delivery, not exactly-once.
  • Keep handlers deterministic and side-effect aware.
  • Surface poison-message handling strategy.

Progressive disclosure

  • Use this file for execution posture and risk controls.
  • Open references when deep implementation details are needed.

Output contract

  • Async config/handlers updated.
  • Retry/failure policy decisions.
  • Operational validation evidence.

References

  • reference.md
  • docs/complexity-tiers.md

Related skills

How it compares

Choose symfony:symfony-scheduler over generic cron docs when jobs must live inside Symfony Messenger with retries, failure transports, and PHP-native observability.

FAQ

Does symfony:symfony-scheduler require Symfony 7.x?

symfony:symfony-scheduler targets the Symfony Scheduler component native since Symfony 7.x. The skill defines schedules and triggers integrated with Messenger for recurring PHP background work instead of manual crontab entries.

What delivery semantics does symfony:symfony-scheduler assume?

symfony:symfony-scheduler assumes at-least-once Messenger delivery, not exactly-once. Handlers must stay idempotent and side-effect aware, with explicit retry, failure-transport, and poison-message handling documented.

PHP & Laravelbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.