Interactive skill to migrate legacy project architecture toward a defined target design.
Install
mkdir -p .claude/skills/redesign && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10285" && unzip -o skill.zip -d .claude/skills/redesign && rm skill.zipInstalls to .claude/skills/redesign
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
redesigns copilot/architecture.md for legacy code into a target architecture.Key capabilities
- →Analyze legacy architecture
- →Propose target components
- →Generate migration steps
- →Create debt tickets
How it works
It iteratively discusses architecture with the user to define a target state and migration path.
Inputs & outputs
When to use redesign
- →Evolve legacy code to a clean architecture
- →Generate architecture debt tickets
- →Plan a transition to new module structures
About this skill
Goal
- Evolve the legacy architecture toward a clean target design.
Phase 1 - Load
- Load
copilot/context.md,copilot/analysis.md(from theanalyseskill), and currentcopilot/architecture.mdif present from the target project.
Phase 2 - Target design
- Propose target components/modules/interfaces.
- Show migration path current -> target.
- Discuss with the user what you found, ask questions about the code, the architecture and the context. Clarify your understanding of the code, architecture, gaps, problems, code quality and so on.
- After a few questions - max 5. - ask the user if he wants to progress to phase 3 or in case you do not have more questions progress to phase 3.
Phase 3 - Select
- Let the user pick what to keep. Simple by questions for each idea: Do not ask the user to pick between ideas, but ask for each idea if he wants to keep it or not. Do not ask the user to rate ideas by value vs effort, but do it yourself based on the discussion with the user and your understanding of the project. Add it to the question like this "Do you want to keep this idea? yes/no/optional user input".
- Then progress to phase 4 with the selected ideas.
Phase 4 - Apply
- Update
copilot/architecture.mdwith the findings.
When not to use it
- →Greenfield projects
- →Projects without existing architecture documentation
Prerequisites
Limitations
- →Requires existing analysis files
- →Limited to 5 clarification questions
How it compares
It facilitates a collaborative design process rather than generating a static architecture document.
Compared to similar skills
redesign side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| redesign (this skill) | 0 | 2mo | No flags | Intermediate |
| brainstorming | 93 | 4mo | Review | Beginner |
| create-plan | 36 | 8mo | Review | Beginner |
| project-planner | 32 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
brainstorming
obra
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
confidence-check
SuperClaude-Org
Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).