rewrite-plan
Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.
Profile →npx skills add nexu-io/open-design --skill rewrite-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Rewrite plan Spec §20.3 / §21.3.2: scenario 4 (design → deliverable production code) requires a contract-shaped rewrite plan before the agent starts editing files. The plan is **the audit trail** every subsequent stage references; without it the patch path slides into "refactor everything that looks wrong" and the build breaks in unreviewable ways. ## Inputs - `code/index.json` from `code-import`. - `token-map/*.json` from `token-map`. - The active design system DESIGN.md (already in prompt). - The user's tune intent (typically a short brief). ## Output ```text project-cwd/ └── plan/ ├── plan.md # human-readable narrative ├── ownership.json # { file: '...', layer: 'leaf' | 'shared' | 'route' | 'shell' } ├── steps.json # ordered { id, files[], rationale, risk: 'low' | 'medium' | 'high' }[] └── meta.json # { generatedAt, atomDigest, tokenMapDigest } ``` `steps.json` is the input `patch-edit` reads one entry per iteration. `ownership.json` is the source of truth for "which files belong to a single component vs. shared infrastructure"; `patch-edit` refuses to touch a `shell`-tier file unless the matching step has `risk: 'high'` and the user explicitly confirmed. ## Convergence The at
- Inputs
- Output
- Convergence
- Anti-patterns the prompt fragment forbids
- Status
What does the rewrite-plan skill do?
Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.
How do I install it?
Run `npx skills add nexu-io/open-design --skill rewrite-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.