mcpField
W
writing-plans

writing-plans

github.com/dev-toolingsAgent workflows22780 installsUpdated 4w ago
Repository

About writing-plans

A Symfony-focused skill for preparing reviewable implementation plans before coding. It structures work across layers into testable steps, with dependencies, acceptance criteria, risks, and reviewer questions.

Key features

  1. 01Define scope and dependencies
  2. 02Design entities, services, and APIs
  3. 03Break work into tested atomic steps
  4. 04Record sizes, acceptance criteria, and risks
  5. 05List reviewer questions

Use cases

  1. 01Planning a feature across several application layers
  2. 02Preparing work for review before coding
  3. 03Splitting implementation across sessions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dev-toolings/superpowers-symfony --skill writing-plans

After installing, type/writing-plansin Claude Code to confirm it loaded.

Bundled filesreference.md

Details

From the project README

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

Comments

Markdown supported