Skip to content
Get packs

Rewrite Plan Author

Writes a structured, step-by-step plan for multi-file code rewrites before any editing begins.

Source Download skill
Repository
nexu-io/open-design
Stars
105,448
Licence
Apache-2.0
Files
2 files

What it does

Before an agent edits a codebase in a large migration or conversion, this skill makes it write a plan first. The plan is a set of files: a readable narrative, a list of which files belong to individual components versus shared infrastructure, and an ordered list of small steps each tagged with a risk level. Later editing stages are meant to follow this plan one step at a time, so changes stay bounded and reviewable instead of sprawling.

Great for

  • Developers converting a design or prototype into production code who want an audit trail of planned changes
  • Teams running multi-file refactors that need per-component steps and explicit ownership boundaries
  • People using the Open Design pipeline who need the planning stage before patch-edit and build-test stages

Skip it if

  • Small single-file edits, where a plan adds overhead without benefit
  • Anyone expecting the skill to perform the rewrite itself: it only writes the plan, and the file has no editing logic of its own in the provided text
  • Use outside the Open Design pipeline, since the SKILL.md refers to other stages (code-import, token-map, patch-edit, build-test) that may not exist in another setup

Try asking

  • “Create a rewrite plan for converting this design export into production React components, split into per-component steps”
  • “Plan the migration of our shared component library, with ownership classified as leaf, shared, route, or shell files”
  • “Draft a step-by-step refactor plan for these files, with a build-test step at the end”
Step-by-step guide: how to use Rewrite Plan AuthorInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the Apache-2.0 licence and an attribution note.

    rewrite-plan.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip rewrite-plan.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip rewrite-plan.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Run code-import and token-map first, since the plan depends on their outputs
  • Review plan.md and steps.json before running patch-edit, because later stages follow these steps
  • Expect shell-tier files to require a high-risk step and explicit user confirmation before they are touched

What's inside

  • open-design.json
  • SKILL.md

Redistributed unmodified from nexu-io/open-design under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.