agentleFS
Sign inStart free
gerard-labsgerard-labs/superpowers-api-platform/skills/writing-plans/SKILL.md

writing-plans

Skill2 starsChanged 6 months agoMITView on GitHub

Create structured implementation plans for non-API-Platform features (Doctrine entity design, refactor cross-skill, infra changes, monorepo migrations). Outputs a step-by-step plan with explicit dependencies, AC, and validation commands. NOT used inside the API Platform pipeline (`/api-resource-pipeline` / `/api-resource-ship`) — that pipeline has its own `api-platform-architect` stage which produces the plan. Use for hors-pipeline plans.

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +2 more from Leodorareluctant259
  • +6 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use existing project patterns by default.

    line 28
  2. Distinctive:

    Avoid broad refactors without explicit need.

    line 29
  3. Distinctive:

    Keep decision log clear and auditable.

    line 30
  4. Distinctive:

    Use this file for posture + decision tree.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 169 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Writing plans (hors pipeline)

Use when

  • Designing a non-API-Platform feature (Doctrine entity, refactor, infra)
  • Planning a multi-skill refactor (/api-resource-pipeline doesn't cover this)
  • Planning a migration that touches multiple sub-projects (monorepo case)
  • Pre-implementation design with explicit dependencies + AC

Not for: API Platform features. Use /api-resource-pipeline or /architect <story> instead — the api-platform-architect agent produces the canonical 9-section plan including the test matrix and skill dispatch list.

Default workflow

  1. Establish current boundaries, constraints, coupling points.
  2. List explicit dependencies (what skills / packages / migrations the plan touches).
  3. Propose the smallest coherent step.
  4. Define acceptance criteria + validation commands per step.
  5. Summarize trade-offs and follow-up backlog.

Guardrails

  • Use existing project patterns by default.
  • Avoid broad refactors without explicit need.
  • Keep decision log clear and auditable.
  • For API Platform-specific plans: redirect to /architect (canonical 9-section plan with verbatim Aligned-Reviewer + AppSec blocks).

Progressive disclosure

  • Use this file for posture + decision tree.
  • Open reference.md for the deeper plan template.
  • Open docs/complexity-tiers.md for sizing.

Output contract

  • Step-by-step plan (numbered, with dependencies)
  • AC + validation per step
  • Trade-offs documented
  • Follow-up backlog

References

  • reference.md
  • docs/complexity-tiers.md
  • docs/symfony/pipeline-overview.md — for the API Platform pipeline alternative

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free