decomposition-planning-roadmap

Creates phased decomposition roadmaps and prioritized migration plans for monolith-to-services transitions.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Peterson-Benhame/agent-skills --skill decomposition-planning-roadmap-peterson-benhame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decomposition-planning-roadmap
Source: https://github.com/Peterson-Benhame/agent-skills/tree/main/packages/skills-catalog/skills/%28architecture%29/decomposition-planning-roadmap
Command: npx skills add https://github.com/Peterson-Benhame/agent-skills --skill decomposition-planning-roadmap-peterson-benhame

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking a monolithic application into distributed services without a structured plan leads to missed dependencies, unrealistic timelines, and stalled migrations. This Skill assesses the current state of decomposition, prioritizes work by risk and value, and produces a phased roadmap with milestones, architecture stories, and progress tracking. ## Core Features & Use Cases - Current State Assessment: Evaluates which of the six component-based decomposition patterns (identify, gather, flatten, analyze dependencies, group domains, extract services) are complete, in progress, or not started. - Prioritization Framework: Scores work items using a formula based on value, risk, and dependencies, and maps them onto a value/risk prioritization matrix. - Phased Roadmap & Stories: Generates phased roadmaps with milestones and timelines, plus architecture stories with acceptance criteria and story-point estimates. - Use Case: An architect planning a monolith-to-microservices migration asks for a decomposition roadmap and receives a current-state assessment, a three-phase plan with weekly milestones, a prioritized work plan, and a progress dashboard. ## Quick Start Ask the agent to create a decomposition roadmap for this codebase based on the current component analysis.

Frequently Asked Questions about decomposition-planning-roadmap

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

FAQPage Schema
How do I create a monolith to microservices migration roadmap?

Start by assessing which decomposition patterns are complete, then prioritize remaining work by risk, value, and dependencies. Group the work into phases such as analysis, domain organization, and service extraction, each with milestones and deliverables.

What order should I extract services from a monolith?

Extract services after completing component identification, flattening, dependency analysis, and domain grouping. Prioritize low-risk, high-value components with few dependencies first, and defer high-risk core business logic until feasibility is validated.

How do I prioritize decomposition work between components?

Score each work item with the formula Priority = (Value × 3) - (Risk × 2) - (Dependencies × 1). High-value, low-risk items are done first, while low-value, high-risk items are deferred or avoided.

When should I not use decomposition planning?

Do not use it for domain analysis or component sizing, which are handled by dedicated skills. It is also unsuitable before any component inventory exists, since the roadmap depends on assessed current state.

How long does a typical monolith decomposition take?

Small projects take 3-6 months, medium projects 6-12 months, and large projects over 12 months. Timelines depend on component count, coupling, and how much analysis work is already complete.