home / skills / makfly / superpowers-symfony / bootstrap-check

bootstrap-check skill

safe

This skill guides production-grade Symfony bootstrap checks, coordinating architecture changes, checkpoints, and auditable risk decisions for safer releases.

npx playbooks add skill makfly/superpowers-symfony --skill bootstrap-check

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.1 KB

---

name: symfony:bootstrap-check
allowed-tools:
  - Read
  - Glob
  - Grep
description: Apply production-grade Symfony architecture and execution workflows with controlled scope and clear checkpoints. Use for bootstrap check tasks.
---

# Bootstrap Check (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.
2. Execute in checkpoints with validation at each stage.
2. 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`

Overview

This skill applies a production-grade Symfony architecture and execution workflow to bootstrap check tasks. It frames changes with a controlled scope and clear checkpoints to reduce risk. The goal is safe, incremental improvements that are auditable and easy to validate.

How this skill works

The skill inspects current boundaries, constraints, and coupling points in your Symfony codebase to establish a baseline. It proposes the smallest coherent architectural adjustment, then defines and executes checkpointed steps with validation criteria. Each checkpoint records outcomes, residual risks, and recommended follow-up tasks for an auditable decision trail.

When to use it

Refining architecture or context-handling in Symfony projects.
Planning medium to complex changes that need staged validation.
When you must avoid broad refactors and prefer incremental, reversible work.
Before deploying workflow or execution changes to production.
When a clear decision log and risk assessment are required.

Best practices

Default to existing project patterns and conventions to minimize disruption.
Limit each change to the smallest coherent scope that fulfills the goal.
Define explicit validation criteria for each checkpoint before implementation.
Keep a concise decision log that captures rationale, tradeoffs, and authorship.
Avoid bulk refactors; escalate only when safety and tests permit.

Example use cases

Introduce a request context service with a single, tested consumer and rollout in checkpoints.
Migrate a portion of services to constructor injection, validating behavior per module.
Add a background job workflow with staged worker deployment and health checks.
Standardize controller input validation by implementing a shared validator and validating on a feature-by-feature basis.
Establish execution timeout and retry policies for a subsystem with checkpointed monitoring.

FAQ

What outputs will I get after a bootstrap check?

You will receive proposed architecture/workflow changes, checkpoint validation results, a residual risk summary, and a prioritized follow-up backlog.

How do checkpoints reduce risk?

Checkpoints enforce small, testable changes with predefined validation criteria and rollback paths, making issues visible early and limiting blast radius.