skills.rest
tulgardinc
tulgardincCOMMUNITY
Explore all skills by this author →
GitHub

architect-refactor

Plan end-to-end refactor architectures with dependency mapping and staged migration steps.

2|Updated Mar 16, 2026
Search Tags:#planning#architecture#documentation#dependencies#migration#refactor#risk
One-click install
npx skills add https://github.com/tulgardinc/vibe-check --skill architect-refactor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-refactor
Source: https://github.com/tulgardinc/vibe-check/tree/main/.claude/skills/architect-refactor
Command: npx skills add https://github.com/tulgardinc/vibe-check --skill architect-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative architecture planning for refactors, mapping dependencies, and ensuring safe, incremental changes that preserve behavior.

Core Features & Use Cases

  • Map dependencies and blast radius across the codebase.
  • Design safe transformation sequences, phased migrations, and contract-driven changes.
  • Produce a step-by-step implementation plan with documentation to guide teams.

Quick Start

Initiate a refactor session with /new-refactor and run architect-refactor to collaboratively map dependencies and draft a step-by-step migration plan.

Frequently Asked Questions about architect-refactor

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

FAQPage Schema
How do I plan a large codebase refactor without breaking existing behavior?▼

To plan a large codebase refactor without breaking behavior, you need to map dependencies, assess risks, and design staged execution. This approach enforces behavioral preservation and outputs a testable migration plan.

What is the best way to map dependencies and blast radius before a structural migration?▼

Mapping dependencies and blast radius involves analyzing the codebase to identify connected components before a structural migration. This process highlights risk areas, enabling the design of safe transformation sequences and contract-driven changes.

How do I create a step-by-step migration plan for complex codebase changes?▼

Creating a step-by-step migration plan for complex codebase changes requires designing phased migrations and documenting decisions. This produces a clearly sequenced implementation plan that guides teams through safe, incremental updates.

When do I need contract-driven changes for a codebase migration?▼

You need contract-driven changes for a codebase migration when structural modifications involve many dependencies and high risk. This approach documents contracts and decisions to ensure safe, incremental changes that preserve system behavior.

Does this architecture planning approach work for incremental refactoring?▼

Yes, this architecture planning approach works for incremental refactoring by designing safe transformation sequences. It supports phased migrations, enforces behavioral preservation, and outputs a testable plan for structural changes.

Related Skills

Explore More Software Engineering Skills→
lasswelltlasswellt
1

codebase-map

Analyze a codebase across technology, architecture, quality, and concerns to generate CODEBASE-MAP.md.

Community
Advanced
CapatainaCapataina

architect-refactor

Map dependencies and generate step-by-step migration plans for codebase refactors.

Community
Advanced
Design-System-ETDesign-System-ET

chaos-engineer

Design and execute chaos experiments to validate system resilience in distributed environments.

Official
Advanced
alangebalangeb

code-review-workflow

Run pyscan, pyanalyze, ruff, and black to generate a unified markdown report.

Community
Intermediate