---
name: Symfony Daily Workflow
slug: symfony-daily-workflow
category: Automation
description: Symfony Daily Workflow guides planning and executing medium-complexity Symfony changes with checkpoints, validation, and clear risk handling. Use it for architecture adjustments, debugging, and safe day-to-day development work.
github: "https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/daily-workflow"
language: TypeScript
stars: 208
forks: 20
install: "npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/daily-workflow ~/.claude/skills/daily-workflow"
installs_to: ~/.claude/skills/daily-workflow
source_path: skills/daily-workflow/SKILL.md
collection_size: 23
category_size: 1860
collection_url: "https://dirskills.com/collections/dev-toolings/superpowers-symfony"
added: 2026-09-04T05:27:06.088Z
last_synced: 2026-09-04T05:27:06.088Z
canonical_url: "https://dirskills.com/skills/symfony-daily-workflow"
---

# Symfony Daily Workflow

Symfony Daily Workflow guides planning and executing medium-complexity Symfony changes with checkpoints, validation, and clear risk handling. Use it for architecture adjustments, debugging, and safe day-to-day development work.

**Install:**

```bash
npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/daily-workflow ~/.claude/skills/daily-workflow
```

## README

# Daily Workflow (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
- `reference.md`
- `docs/complexity-tiers.md`
