symfony-scheduler_skill

This skill helps implement resilient Symfony async workflows with idempotent handlers, retries, and observability for scheduler tasks.
  • Shell

69

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill makfly/superpowers-symfony --skill symfony-scheduler

  • reference.md8.6 KB
  • SKILL.md1.1 KB

Overview

This skill helps implement resilient asynchronous workflows for Symfony Scheduler, focusing on idempotency, retries, and operational visibility. It provides guidance to update async contracts, handlers, and retry/failure policies to operate reliably under at-least-once delivery. The result is a hardened scheduler setup with clear operational controls and validation steps.

How this skill works

The skill inspects your async contract, delivery semantics, and handler implementations to identify non-determinism and side effects. It recommends idempotency patterns, routing and retry configuration for Symfony Messenger/Scheduler, and a failure transport strategy. It also defines observable signals and validation steps to prove safe replay and recovery.

When to use it

  • Building or refactoring Symfony async tasks backed by Messenger/Scheduler
  • Stabilizing systems that experience duplicate deliveries or flaky retries
  • Defining operational controls for scheduled jobs and failure transports
  • Preparing systems for safe replays or disaster recovery testing

Best practices

  • Assume at-least-once delivery; design handlers to tolerate duplicates and partial runs
  • Make handlers idempotent by using dedup keys, versioned state, or transactional checkpoints
  • Keep handlers deterministic: avoid non-repeatable external calls without compensation
  • Centralize retry and failure transport policies; treat poison messages explicitly
  • Add observability: structured logs, metrics for retries/poisons, and replay audit trails

Example use cases

  • Convert scheduler tasks that mutate external systems into idempotent command handlers with dedup keys
  • Configure Messenger retry and failure transport with clear escalation paths for human review
  • Validate replay scenarios by running recorded inputs against handlers in a sandbox and asserting idempotent outcomes
  • Instrument scheduler jobs to emit retry and failure metrics and integrate with alerting
  • Implement a poison-message handler that quarantines and annotates failed payloads for manual triage

FAQ

No. This skill assumes at-least-once delivery and focuses on idempotency and safe retries rather than trying to enforce exactly-once at the transport level.

How do I validate that replays are safe?

Capture representative inputs and run them against handlers in an isolated environment. Verify state is unchanged for retried payloads or that compensating actions are applied deterministically.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
symfony-scheduler skill by makfly/superpowers-symfony | VeilStrat