Agent skill · Databases

decomposition-planning-roadmap

Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices strategy", or tracking decomposition progress. Do NOT use for domain analysis (use domain-analysis) or component sizing (use component-identification-sizing).

tech-leads-clubgithub.com/tech-leads-clubGitHub ↗
claude-codecopilotcursorNOASSERTION
Install
npx skills add tech-leads-club/agent-skills --skill decomposition-planning-roadmap --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 17 KB
Bundled scripts: none
Path: packages/skills-catalog/skills/(architecture)/decomposition-planning-roadmap/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 4,983
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Decomposition Planning and Roadmap This skill creates structured decomposition plans and roadmaps to guide the migration from monolithic to distributed architectures, prioritizing work and tracking progress through decomposition patterns. ## How to Use ### Quick Start Request creation of a decomposition plan: - **"Create a decomposition roadmap for this codebase"** - **"Plan the decomposition migration strategy"** - **"Prioritize decomposition work based on component analysis"** - **"Create a step-by-step decomposition plan"** ### Usage Examples **Example 1: Complete Roadmap** ``` User: "Create a decomposition roadmap for this codebase" The skill will: 1. Analyze current codebase state 2. Identify decomposition patterns to apply 3. Prioritize work based on risk and value 4. Create phased roadmap 5. Generate architecture stories 6. Estimate effort and dependencies ``` **Example 2: Prioritized Plan** ``` User: "Prioritize decomposition work based on component analysis" The skill will: 1. Review component inventory and dependencies 2. Assess risk and value for each pattern 3. Prioritize patterns by impact 4. Create prioritized work plan ``` **Example 3: Phase Planning** ``` User: "C

What's inside
Steps it walks through
  1. How to Use
  2. Quick Start
  3. Usage Examples
  4. Step-by-Step Process
  5. When to Use
  6. Core Concepts
  7. Decomposition Pattern Sequence
  8. Phased Approach
  9. Prioritization Factors
  10. Analysis Process
  11. Phase 1: Assess Current State
  12. Phase 2: Identify Patterns to Apply
  13. Phase 3: Prioritize Work
  14. Phase 4: Create Phased Roadmap
Ships with 2 files
  • QUICK-REFERENCE.md
  • README.md
More from agent-skills
All skills →
About this skill
What does the decomposition-planning-roadmap skill do?

Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices strategy", or tracking decomposition progress. Do NOT use for domain analysis (use domain-analysis) or component sizing (use component-identification-sizing).

How do I install it?

Run `npx skills add tech-leads-club/agent-skills --skill decomposition-planning-roadmap --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 tech-leads-club/agent-skills, a repository with 4,983 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.

Keep going