writing-plans · dev-toolings — Claude Code skill: what it does, how to install
writing-plans generates structured implementation plans for Symfony features with clear steps, acceptance criteria, and risk mitigations.
MIT ★ 234 updated 2026-10-05
npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a claude-codeWhat writing-plans does
This skill prepares an engineering plan before writing code across Symfony entities, services, message handlers, or API endpoints. It defines what is in or out of scope, outlines class architecture, and highlights open questions for review.
Work breaks down into atomic steps, with each phase starting from its test. Every step gets a dependency link and a size tag (S, M, or L). For standard scenarios like CRUD, background jobs, or third-party integrations, the workflow relies on templates in reference.md. During drafting, the agent uses only read-only discovery tools: Read, Glob, and Grep.
Vague intentions are explicitly barred. The output must reference concrete file paths, endpoints, and class names, keeping the plan directly actionable.
What it helps with
- plan multi-layer Symfony features across entities, services, and APIs
- split large tasks into test-first atomic steps with sizing
- document acceptance criteria and risks before starting implementation
- explicitly list out-of-scope items to prevent scope creep
Example prompts for the agent
- Write an implementation plan for async report exports in Symfony
- Draft a structured plan to add a billing webhook handler and entities
- Create a step-by-step plan for the user profile API endpoint
How to install writing-plans
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a claude-code2Manually: put the files in place
~/.claude/skills/writing-plans/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/writing-plans/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a codex2Manually: put the files in place
.agents/skills/writing-plans/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a cursor2Manually: put the files in place
.cursor/skills/writing-plans/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dev-toolings/superpowers-symfony content/skills/writing-plans2Manually: put the files in place
.github/skills/writing-plans/SKILL.md1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a gemini-cli2Platform CLI
gemini skills install https://github.com/dev-toolings/superpowers-symfony --path content/skills/writing-plansManually: put the files in place
.devin/skills/writing-plans/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about writing-plans
How to install writing-plans in Claude Code?
Run npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a claude-code. The skill will be placed in ~/.claude/skills/writing-plans/SKILL.md.
What does writing-plans do?
It structures planned work into phased steps, class changes, and acceptance criteria before implementation starts.
Which templates are included in reference.md?
It provides starting templates for CRUD features, background workers, and external integrations.
Source text
SKILL.md · MIT
--- name: writing-plans description: Create structured implementation plans for Symfony features with clear steps, dependencies, and acceptance criteria capabilities: [read, search] tags: [workflow] # projected by `bun run build` — do not edit by hand allowed-tools: - Read - Glob - Grep --- # 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. - Open questions for the reviewer. ## References - `reference.md`
© dev-toolings · MIT · dev-toolings/superpowers-symfony
Similar skills
All skills for Backend and APIs →writing-plans by other authors comes first.