feature-decompose

Decompose large features into sequenced PRs with dependency graphs.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/AdemKao/ai-cowork --skill feature-decompose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-decompose
Source: https://github.com/AdemKao/ai-cowork/tree/main/.ai/skills/feature-decompose
Command: npx skills add https://github.com/AdemKao/ai-cowork --skill feature-decompose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposes large features into manageable PRs with clear dependencies, enabling safer reviews and smoother integration.

Core Features & Use Cases

  • Dependency graph generation to map PR relationships across features
  • Structured PR breakdown and phased execution planning
  • Cross-team coordination guidance to maximize parallel work while avoiding conflicts

Quick Start

Outline your feature into a sequence of PRs with clear dependencies to enable incremental review.

Frequently Asked Questions about feature-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 smaller pull requests?

Feature decomposition maps PR relationships by generating a dependency graph, which structures execution planning and guides cross-team coordination to maximize parallel work while avoiding conflicts.

Can I use feature decomposition for both API service changes and UI updates?

Feature decomposition is suitable for mid-to-large feature work across software projects. It requires outlining your feature to generate a dependency graph and structured PR breakdown for phased execution planning.

What is the best way to plan a dependency graph for a complex PR sequence?

Feature decomposition enables safer, faster reviews by structuring PR breakdowns into focused, manageable units with clear dependencies, avoiding the bottlenecks and integration conflicts of large, monolithic pull requests.

How do I manage cross-team coordination when splitting a feature into multiple PRs?

You manage cross-team coordination by generating a dependency graph to map PR relationships, which maximizes parallel work while avoiding conflicts during the phased execution of your feature.