skills.rest
Gabr1elaugus700
Gabr1elaugus700COMMUNITY
Explore all skills by this author →
GitHub

decomposition-planning-roadmap

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

1|Updated Apr 25, 2025
Search Tags:#microservices#prioritization#decomposition#monolith#architecture planning#service extraction#migration roadmap
One-click install
npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill decomposition-planning-roadmap-gabr1elaugus700
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decomposition-planning-roadmap
Source: https://github.com/Gabr1elaugus700/WorkaPool/tree/main/.windsurf/skills/decomposition-planning-roadmap
Command: npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill decomposition-planning-roadmap-gabr1elaugus700

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking a monolithic application into distributed services is hard to sequence: teams struggle to decide what to extract first, how to prioritize work by risk and value, and how to track progress across a long migration effort. ## Core Features & Use Cases - Current State Assessment: Evaluates which of the six component-based decomposition patterns (identify, gather, flatten, analyze dependencies, create 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 Roadmaps & Architecture Stories: Generates phased roadmaps with milestones and timelines, plus architecture stories with acceptance criteria and story-point estimates. - Use Case: Ask for a decomposition roadmap for your codebase and receive a current-state assessment, a phased plan (Analysis, Domain Organization, Service Extraction), a prioritized work plan, and a progress dashboard. ## Quick Start Ask the assistant to create a decomposition roadmap for this codebase with prioritized phases and architecture stories.

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?▼

Request a decomposition roadmap and the skill assesses your current state, identifies which of the six decomposition patterns to apply, prioritizes work by risk and value, and produces a phased roadmap with milestones, timelines, and architecture stories.

How do I prioritize which services to extract first from a monolith?▼

Prioritize using the formula Priority = (Value × 3) - (Risk × 2) - (Dependencies × 1). Start with low-risk, high-value components such as infrastructure or standalone functionality, and defer high-risk core business logic until dependencies are resolved.

What order should decomposition patterns be applied in?▼

Apply the six patterns in sequence: identify and size components, gather common domain components, flatten components, determine component dependencies, create component domains, then create domain services. Skipping analysis patterns before extraction is discouraged.

When should I not use this decomposition planning skill?▼

Do not use it for domain analysis or component sizing tasks; those belong to the domain-analysis and component-identification-sizing skills. This skill focuses on planning, prioritization, and progress tracking, not the underlying analysis itself.

How long does a typical monolith decomposition take?▼

The skill provides templates by project size: small projects take 3-6 months, medium projects 6-12 months, and large projects 12+ months. Timelines are split across analysis, domain organization, service extraction, and optimization phases.

Related Skills

Explore More Software Engineering Skills→
MatheusrlrMatheusrlr
1

component-identification-sizing

Identify architectural components and calculate size metrics from directory and namespace structures.

Community
Intermediate
a53alia53ali

monolith-to-services

Decompose monolithic applications into microservices using Domain-Driven Design.

Community
Advanced
AO-Cyber-SystemsAO-Cyber-Systems

df:list-objective-assumptions

Surfaces Claude's assumptions about scope, risks, and implementation for a given objective.

Official
Advanced
rodrigo-altissimorodrigo-altissimo

software-engineering-eng-ddd

Analyze business domains to produce bounded contexts, aggregates, and ubiquitous language.

Community
Advanced