decomposition-planning-roadmap SKILL.md skillA
decomposition-planning-roadmap from tech-leads-club/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tech-leads-club/agent-skills/decomposition-planning-roadmap@git:20260226.8dca459Pins git:20260226.8dca459 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(architecture)/decomposition-planning-roadmap/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260226.8dca459, committed Feb 26, 2026
- First version recorded
- Feb 6, 2026
- Size
- 17,282 bytes
- Repository stars
- 7,124
- License
- a license file GitHub does not identify
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).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 ``` …
Read the whole file at its exact version.
How to install
mdr add tech-leads-club/agent-skills/decomposition-planning-roadmap@sha256:b0f6f55affb07a2cThe line at the top of this page pins the label git:20260226.8dca459, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_cmfx7ppzsjpky3xv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Feb 6, 2026 and Feb 26, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260226.8dca459 latest | 2026-02-26 | 8dca459 | 17,282 B | A | view · diff |
| git:20260206.959e3d9 | 2026-02-06 | 959e3d9 | 17,165 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17282 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tech-leads-club/agent-skills · 7,124 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cmfx7ppzsjpky3xv GET https://markdownregistry.com/api/v1/resolve?ref=tech-leads-club/agent-skills/decomposition-planning-roadmap GET https://markdownregistry.com/api/v1/blob/b0f6f55affb07a2c70516f421293567683f5ae15632917f968e1366e7b1aa4a8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.