Methodically execute implementation plans with a TDD approach, incremental commits, and continuous validation.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Executing Plans (Symfony)
## Use when
- An approved implementation plan exists and must be carried out.
- The work spans several steps that must each land green.
- Resuming a plan after an interruption or a blocker.
## Default workflow
1. Read the whole plan, confirm the baseline tests pass, and work on a branch.
2. For each step, write the test, watch it fail, implement, watch it pass, then refactor.
3. Commit after each completed step, with a message that names it.
4. Run the quality gates (style, static analysis, full suite) at the end of each phase.
5. Track each step's status in the plan, and stop to report when reality contradicts it.
## Guardrails
- Never skip watching the test fail: a test that never failed proves nothing.
- One step per commit; do not batch steps.
- Do not change the plan silently: report the deviation and the reason.
- On a blocker (failing migration, autowiring error), fix the cause, not the test.
## Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
## Output contract
- One commit per step, tests included.
- The plan with the status of every step.
…
The line at the top of this page pins the label git:20261005.06ec807, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_s6smswvttv4skfvh
GET https://markdownregistry.com/api/v1/resolve?ref=dev-toolings/superpowers-symfony/executing-plans
GET https://markdownregistry.com/api/v1/blob/79d2ae54e796f6379f4e7b7e4a6d6e0c539926009ea3542a05118e7db4fa15e9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
dev-toolings/superpowers-symfony · content/skills/api-platform-dto-resources/SKILL.md · Map entities to API DTOs in API Platform (v5, 4.4, 4.3) with the Symfony Object Mapper (#[Map], stateOptions) for…
dev-toolings/superpowers-symfony · content/skills/api-platform-filters/SKILL.md · Implement API Platform filters - Parameters API (QueryParameter, v5/4.4/4.3) and the #[ApiFilter] attribute deprecated…
dev-toolings/superpowers-symfony · content/skills/api-platform-resources/SKILL.md · Configure API Platform resources (v5, 4.4, 4.3) with explicit operations, pagination, and typed OpenAPI for clean…
dev-toolings/superpowers-symfony · content/skills/api-platform-serialization/SKILL.md · Control API Platform serialization with groups, #[Context], IRI links (readableLink/writableLink), and custom context…
dev-toolings/superpowers-symfony · content/skills/api-platform-state-providers/SKILL.md · Master API Platform State Providers and Processors (v5, 4.4, 4.3) (ProviderInterface/ProcessorInterface) to decouple…
dev-toolings/superpowers-symfony · content/skills/api-platform-tests/SKILL.md · Test API Platform resources with ApiTestCase; assert collections, items, filters, JSON schema, and authentication
dev-toolings/superpowers-symfony · content/skills/api-platform-versioning/SKILL.md · Evolve API Platform APIs via deprecation (deprecationReason/sunset, RFC 8594/9745), the recommended alternative to…
obra/superpowers · skills/executing-plans/SKILL.md · Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose…
a5c-ai/babysitter · library/methodologies/superpowers/skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute in a separate session with review checkpoints between…
ganyuanran/aegis · skills/executing-plans/SKILL.md · Use when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice…
coco-research/coco · skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute in a separate session with review checkpoints
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute in a separate session with review checkpoints
jamditis/claude-skills-journalism · superjawn/skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute in a separate session with review checkpoints
ibrahim-3d/orchestrator-supaconductor · skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute in a separate session with review checkpoints
