Monolith Assessment

Evaluate whether to keep, refactor, or break apart a monolithic system. Use when facing scaling or team velocity challenges with monoliths.

48 stars 10 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill monolith-assessment
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/system-design/skills/monolith-assessment ~/.claude/skills/monolith-assessment

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Monolith Assessment

Systematically evaluate a monolithic system to determine the right evolution path: stay monolith, strangler fig, distributed monolith, or true microservices.

## Context

You are analyzing a monolithic system. The user is experiencing pain (scaling, slow deployment, team conflicts) and needs objective guidance on whether to split services or optimize the monolith. Read code samples, deployment info, and team structure.

## Domain Context

Based on Sam Newman, Martin Fowler, and Shopify's monolith journey:

- **Two-Pizza Team Rule**: Effective team size for one codebase is ~8-10 engineers; beyond that, splitting accelerates
- **Deployment Coupling**: Cannot deploy independently → services should separate
- **Data Coupling**: Services share databases → integration tighter than desired
- **Strangler Fig Pattern**: Incrementally replace monolith pieces without full rewrite
- **Inverse Conway's Law**: System architecture mirrors team structure; if teams are independent, system should be

## Instructions

1. **Score Pain Dimensions**: Rate the monolith on (1-5): deployment frequency, team wait times, scaling per component, technology brittleness. High scores indicate split pressure.

2. **Map Team Structure**: How many teams? Do they work independently? Are code conflicts blocking? If >3 teams, monolith is likely bottleneck.
Read the full skill on GitHub

Details

Skill name
monolith-assessment
Path
architect/system-design/skills/monolith-assessment/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Monolith Assessment skill do?

Evaluate whether to keep, refactor, or break apart a monolithic system. Use when facing scaling or team velocity challenges with monoliths.

How do I install the Monolith Assessment skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Monolith Assessment popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.