skills.rest
nexu-io
nexu-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

rewrite-plan

Generate structured multi-file migration plans with defined ownership boundaries and patch-safety guarantees.

93.2k|10.8k|Updated Apr 28, 2026
Search Tags:#design-system#Refactoring#Planning#code-migration#ARCHITECTURE#patch-safety
One-click install
npx skills add https://github.com/nexu-io/open-design --skill rewrite-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rewrite-plan
Source: https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/rewrite-plan
Command: npx skills add https://github.com/nexu-io/open-design --skill rewrite-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the chaos of large-scale code migrations where uncoordinated edits lead to broken builds and unreviewable diffs by enforcing a formal planning stage before any code is modified.

Core Features & Use Cases

  • Ownership Mapping: Automatically classifies files into layers (leaf, shared, route, shell) to prevent accidental modification of critical infrastructure.
  • Step-by-Step Execution: Generates a structured steps.json file that guides subsequent patch-edit tools through safe, iterative changes.
  • Use Case: When migrating a legacy component library to a new design system, use this Skill to audit the codebase, define component boundaries, and generate a risk-assessed plan that ensures the build remains stable throughout the process.

Quick Start

Analyze the current codebase and generate a multi-file rewrite plan based on the active design system.

Frequently Asked Questions about rewrite-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a safe migration plan for large codebases?▼

Use the rewrite-plan skill to generate a structured audit trail that breaks down complex migrations into discrete, risk-assessed steps. This ensures every file modification is tracked and aligned with your design system requirements.

What is the purpose of the ownership.json file?▼

The ownership.json file defines the architectural layer of each file, such as leaf, shared, or shell. This prevents automated tools from modifying critical infrastructure unless the user explicitly confirms a high-risk operation.

Can I use this skill for partial component refactoring?▼

Yes, the skill is designed to break down large-scale library rewrites into per-component steps. This granular approach prevents the anti-pattern of attempting to rewrite an entire library in a single, unreviewable operation.

Does this skill execute the code changes?▼

No, this skill focuses on the planning and audit phase. It generates the necessary plan.md, steps.json, and ownership.json files that are subsequently consumed by patch-edit tools to perform the actual code migration.

Related Skills

Explore More Software Engineering Skills→
smallnestsmallnest
207

code-to-spec

Analyze source structure and generate a structured SPEC document from an existing codebase.

Community
Advanced
NintendaDevNintendaDev
16

unikit-fix

Automate end-to-end bug-fix workflows in UniKit AI projects.

Community
Advanced
AnExiledDevAnExiledDev
9

migration-patterns

Coordinate codebase migrations with stepwise plans, build/test verification, and rollback checkpoints.

Community
Advanced
suhwansuhwan

ultrapilot

Coordinate parallel automation tasks with exclusive file ownership across modules.

Community
Advanced