writing-plans SKILL.md skillA
writing-plans from dev-toolings/superpowers-symfony is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dev-toolings/superpowers-symfony/writing-plans@git:20261005.06ec807Pins git:20261005.06ec807 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dev-toolings/superpowers-symfony
- Path
content/skills/writing-plans/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261005.06ec807, committed Oct 5, 2026
- First version recorded
- Sep 17, 2026
- Size
- 1,563 bytes
- Repository stars
- 231
- License
- MIT
Create structured implementation plans for Symfony features with clear steps, dependencies, and acceptance criteria.
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
# Writing Plans (Symfony) ## Use when - A feature touches several layers: entities, services, API, async work. - The work must be reviewed, or split across sessions, before coding starts. - Scope and risks must be known before committing to an approach. ## Default workflow 1. Write the overview: summary, scope in and out, dependencies. 2. Design the changes: new and modified entities, services and handlers, API endpoints. 3. Break the work into phases of atomic steps, each starting with its test. 4. Mark the dependencies between steps and size each one (S, M, L). 5. Write the acceptance criteria, and the risks with their mitigation. ## Guardrails - Every step can be completed and tested on its own. - Name concrete files, classes and endpoints, not intentions. - List what is out of scope instead of dropping it silently. - Start from a template in `reference.md` (CRUD, background job, integration) when one fits. ## Progressive disclosure - Use this file for execution posture and risk controls. - Open references when deep implementation details are needed. ## Output contract - A plan with overview, design, steps, acceptance criteria and risks. - Step dependencies and sizes. …
Read the whole file at its exact version.
How to install
mdr add dev-toolings/superpowers-symfony/writing-plans@sha256:b6bff7f3ba52b90eThe 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.
[](https://markdownregistry.com/a/art_ybaugcy7jlmpa7gn)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 17, 2026 and Oct 5, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.06ec807 latest | 2026-10-05 | 06ec807 | 1,563 B | A | view · diff |
| git:20261005.042befb | 2026-10-05 | 042befb | 1,160 B | A | view · diff |
| git:20260917.3d83f4c | 2026-09-17 | 3d83f4c | 1,189 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1563 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
dev-toolings/superpowers-symfony · 231 stars · license MIT · pushed 2026-10-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ybaugcy7jlmpa7gn GET https://markdownregistry.com/api/v1/resolve?ref=dev-toolings/superpowers-symfony/writing-plans GET https://markdownregistry.com/api/v1/blob/b6bff7f3ba52b90ee4d8a107752110ab70efc0ce03671f3f5c1d11169e11fff2
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from dev-toolings/superpowers-symfony
Every file in dev-toolings/superpowers-symfony