decompose

Decompose large software features into ordered, PR-sized shippable steps.

Updated Feb 24, 2026

Search Tags:#workflow #code management #decomposition #agile development #feature breakdown #pr planning

Ready to run

npx skills add https://github.com/metalspawn/claude-ops --skill decompose-metalspawn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decompose
Source: https://github.com/metalspawn/claude-ops/tree/main/skills/decompose
Command: npx skills add https://github.com/metalspawn/claude-ops --skill decompose-metalspawn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps break down large, complex features into smaller, manageable, and independently shippable steps, making the development process more organized and reviewable.

Core Features & Use Cases

Feature Decomposition: Divides a large feature into a series of PR-sized steps.
Dependency Management: Clearly defines the order and dependencies between these steps.
Use Case: Before starting a major architectural change, use this Skill to plan out how to roll it out incrementally across multiple pull requests, ensuring each step delivers value and the codebase remains stable.

Quick Start

Use the decompose skill to break down the feature "Implement user authentication with OAuth2".

Frequently Asked Questions about decompose

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

FAQPage Schema

How do I break down a large software feature into independently shippable PRs?▼

Feature breakdown involves decomposing large changes into a sequence of PR-sized steps. By identifying affected module boundaries and dependencies, you can define ordered steps that each deliver a clear, shippable artifact.

What is the best way to plan an incremental rollout for a major architectural change?▼

Planning an incremental rollout requires defining a sequence of PR-sized steps with clear scope. You must identify affected systems and dependencies to ensure the codebase remains stable and each step delivers value.

How do I manage dependencies when splitting a complex feature into multiple pull requests?▼

Dependency management during feature decomposition requires identifying module boundaries and affected systems. You define the order of PR-sized steps to ensure dependencies are resolved sequentially and each step is independently shippable.

Can I use feature decomposition for iterative development of complex changes?▼

Feature decomposition directly facilitates iterative development for complex changes. It divides large features into a series of manageable, PR-sized steps, making the development process more organized and reviewable.

Does feature breakdown help keep the codebase stable during a major rollout?▼

Feature breakdown keeps the codebase stable by dividing large features into independently shippable steps. Each PR-sized step is defined with clear scope and dependencies, ensuring the system remains functional throughout the rollout.

When do I need to decompose a feature into a sequence of PR-sized steps?▼

You need feature decomposition when planning a major architectural change. It helps break down large, complex features into smaller, manageable steps, ensuring each pull request delivers value and the codebase remains stable.