Planner
penpot/penpot
Read-only planning and architecture analysis — produce a structured implementation plan with task breakdown, acceptance criteria, sizing, and checkpoints.
Create structured implementation plans for Symfony features with clear steps, dependencies, and acceptance criteria
Install Writing Plans
$ npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dev-toolings/superpowers-symfony writing-plans --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .claude/skills && cp -r skills-src/content/skills/writing-plans .claude/skills/writing-plans && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "writing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/writing-plans into .claude/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/writing-plansType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dev-toolings/superpowers-symfony writing-plans --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .agents/skills && cp -r skills-src/content/skills/writing-plans .agents/skills/writing-plans && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/writing-plans into .agents/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dev-toolings/superpowers-symfony writing-plans --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/content/skills/writing-plans .cursor/skills/writing-plans && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/writing-plans into .cursor/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dev-toolings/superpowers-symfony.git --path content/skills/writing-plans--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dev-toolings/superpowers-symfony writing-plans --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/content/skills/writing-plans .gemini/skills/writing-plans && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/writing-plans into .gemini/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dev-toolings/superpowers-symfony writing-plansInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .github/skills && cp -r skills-src/content/skills/writing-plans .github/skills/writing-plans && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/writing-plans into .github/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dev-toolings/superpowers-symfony writing-plans --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/content/skills/writing-plans .opencode/skills/writing-plans && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-plans" agent skill from https://github.com/dev-toolings/superpowers-symfony/tree/main/content/skills/writing-plans into .opencode/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
writing-plans- GitHub stars
- 222
- Token cost
- ~391 tokens
- SKILL.md length
- 186 words
- Files
- 2
- Skills in repo
- 44
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create structured implementation plans for Symfony features with clear steps, dependencies, and acceptance criteria
- Works in 5 steps: Write the overview: summary, scope in… → Design the changes: new and modified… → Break the work into phases of atomic… → …
- Tasks that involve Planning
- SKILL.md covers Use when, Default workflow, Guardrails and Progressive disclosure, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Writing Plans is an agent skill from dev-toolings/superpowers-symfony. Create structured implementation plans for Symfony features with clear steps, dependencies, and acceptance criteria
Its SKILL.md is about 390 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).
It sits in Agent Workflows, covering Planning and User stories. It works with Symfony. The repository describes itself as: Claude Code plugin for Symfony 7.4 LTS & 8.x — 44 skills, 7 AI subagents & 13 commands for API Platform v4, Doctrine ORM 3, TDD (Pest/PHPUnit), Messenger, security & DDD. The licence is MIT.
When your agent uses it
- Tasks that involve Planning
- Tasks that involve User stories
Example prompts
- “/writing-plans”
Requirements
- Pre-approved tools (allowed-tools): Read, Glob, Grep
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Write the overview: summary, scope in and out, dependencies.
- Design the changes: new and modified entities, services and handlers, API endpoints.
- Break the work into phases of atomic steps, each starting with its test.
- Mark the dependencies between steps and size each one (S, M, L).
- Write the acceptance criteria, and the risks with their mitigation.
What it can do on your machine
Read from SKILL.md and the folder at commit 459bcd0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Writing Plans loads about 391 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 186 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dev-toolings/superpowers-symfony at commit 459bcd0, republished under its MIT licence (© dev-toolings). 186 words, ~391 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-plans/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- writing-plans
- description
- Create structured implementation plans for Symfony features with clear steps, dependencies, and acceptance criteria
- allowed-tools
- Read, Glob, Grep
- capabilities
- read, search
- tags
- workflow
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
- Write the overview: summary, scope in and out, dependencies.
- Design the changes: new and modified entities, services and handlers, API endpoints.
- Break the work into phases of atomic steps, each starting with its test.
- Mark the dependencies between steps and size each one (S, M, L).
- 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. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in content/skills/writing-plans of dev-toolings/superpowers-symfony.
- SKILL.md
- reference.md
Open the folder on GitHubat commit 459bcd0
Compare with similar skills
Writing Plans next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Plans this skilldev-toolings/superpowers-symfony | 222 | — | ~391 | Automated safety check: Pass | MIT | |
| Plannerpenpot/penpot | 61k | — | ~2.7k | Automated safety check: Pass | MPL-2.0 | |
| Speckit Tasksforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Planning And Task Breakdownskuramatata/my-pi-agent | 114 | — | ~679 | Automated safety check: Pass | None | |
| Gen Planalibaba/atrex-kernel-agent | 161 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Code Task Generatormikeyobrien/ralph-orchestrator | 3.2k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Speckit Tasks
foryourhealth111-pixel/Vibe-Skills
Break down implementation plans into actionable task lists. An agent skill from foryourhealth111-pixel/Vibe-Skills.
Planning And Task Breakdown
skuramatata/my-pi-agent
A skill your agent uses when my-pi-agent work needs requirement slicing, implementation planning, multi-step ordering, dependency decisions, or clear acceptance criteria before coding.
Gen Plan
alibaba/atrex-kernel-agent
Generate a structured implementation plan from an evidence draft.
Code Task Generator
mikeyobrien/ralph-orchestrator
Generates structured .code-task.md files from descriptions or PDD implementation plans.
Autospec Tasks
ariel-frischer/autospec
Generate YAML task breakdown from implementation plan. An agent skill from ariel-frischer/autospec.
More from dev-toolings/superpowers-symfony
All 44 skills in this repoSymfony Scheduler
dev-toolings/superpowers-symfony
Schedule recurring tasks with the Symfony Scheduler component (native since 7.x); define schedules, triggers, and integrate with Messenger
API Platform Dto Resources
dev-toolings/superpowers-symfony
Map entities to API DTOs in API Platform (v5, 4.4, 4.3) with the Symfony Object Mapper ([Map], stateOptions) for decoupled input/output contracts
API Platform Filters
dev-toolings/superpowers-symfony
Implement API Platform filters - Parameters API (QueryParameter, v5/4.4/4.3) and the [ApiFilter] attribute deprecated since 4.4 - for search, date, range, boolean, and custom filtering
API Platform Resources
dev-toolings/superpowers-symfony
Configure API Platform resources (v5, 4.4, 4.3) with explicit operations, pagination, and typed OpenAPI for clean, versioned REST/GraphQL APIs
API Platform Security
dev-toolings/superpowers-symfony
Secure API Platform resources with security expressions, voters, securityPostValidation, and operation-level access control
API Platform Serialization
dev-toolings/superpowers-symfony
Control API Platform serialization with groups, [Context], IRI links (readableLink/writableLink), and custom context builders
Related
Works with
Categories
Questions about Writing Plans
What does Writing Plans do?
Create structured implementation plans for Symfony features with clear steps, dependencies, and acceptance criteria. Writing Plans is an agent skill from dev-toolings/superpowers-symfony.
When should I use Writing Plans?
Writing Plans fits situations like: tasks that involve Planning; tasks that involve User stories.
How do I install Writing Plans in Claude Code?
Run `npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a claude-code`. Or copy the skill folder (content/skills/writing-plans in dev-toolings/superpowers-symfony) into .claude/skills/writing-plans in your project. Claude Code loads it when a task matches its description.
How do I install Writing Plans in Codex?
Run `npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a codex`. Or copy the skill folder (content/skills/writing-plans in dev-toolings/superpowers-symfony) into .agents/skills/writing-plans in your project. Codex loads it when a task matches its description.
Can I use Writing Plans in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dev-toolings/superpowers-symfony --skill writing-plans -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-plans, .gemini/skills/writing-plans, .github/skills/writing-plans and .opencode/skills/writing-plans in your project.
What does Writing Plans need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Plans is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep.
Does Writing Plans access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Writing Plans safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Writing Plans use?
Writing Plans is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Writing Plans use?
About 391 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Writing Plans?
Skills that share tags, products or a category with Writing Plans: Planner (penpot/penpot, 61k stars), Speckit Tasks (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), Planning And Task Breakdown (skuramatata/my-pi-agent, 114 stars) and Gen Plan (alibaba/atrex-kernel-agent, 161 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Plans?
dev-toolings (a GitHub organization) maintains it in dev-toolings/superpowers-symfony, which has 222 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 5, 2026.
Source: dev-toolings/superpowers-symfony on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.