feature-breakdown

Decompose large features into chunks with a dependency graph.

1|Updated Mar 27, 2026

Search Tags:#planning #scoping #decomposition #dependency-graph #feature-breakdown #work-slicing

Ready to run

npx skills add https://github.com/NEXUZ-SYS/devflow --skill feature-breakdown-nexuz-sys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-breakdown
Source: https://github.com/NEXUZ-SYS/devflow/tree/main/skills/feature-breakdown
Command: npx skills add https://github.com/NEXUZ-SYS/devflow --skill feature-breakdown-nexuz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose large features into actionable chunks to reduce risk and enable parallel work.

Core Features & Use Cases

Map a feature to its user-visible outcomes and success criteria.
Identify system components, boundaries, and interfaces.
Slice work into independently deliverable chunks with dependency guidance.
Generate a dependency graph and plan for parallel execution.
Allocate tasks to agents or teams based on capabilities and workload.

Quick Start

Provide a feature description and let the skill generate a structured breakdown.

Frequently Asked Questions about feature-breakdown

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

FAQPage Schema

How do I decompose large features into actionable chunks for parallel work?▼

Feature breakdown involves mapping a feature to user-visible outcomes, identifying system boundaries, and slicing work into independently deliverable chunks. It generates a dependency graph and agent allocations to reduce risk and enable parallel work.

How do I generate a dependency graph for features spanning multiple components?▼

When planning features spanning multiple systems, feature breakdown identifies system components, boundaries, and interfaces, then slices work into deliverable chunks with a dependency graph. This suits downstream automation and scoping tooling.

What is the best way to scope and plan delivery chunks for downstream automation?▼

Feature breakdown generates a structured output format containing a chunk list, dependency graph, and optional agent allocations. This output is suitable for downstream automation and scoping tooling, enabling teams to coordinate parallel execution.

Can I use feature breakdown to allocate tasks to agents based on capabilities?▼

Yes, feature breakdown includes optional agent allocations that assign tasks to agents or teams based on capabilities and workload. This allocation works alongside the generated chunk list and dependency graph to enable parallel work.

What do I need to provide to start scoping work into independently deliverable chunks?▼

Feature breakdown requires only a feature description to begin. It maps the feature to user-visible outcomes and success criteria, identifies system components, and slices work into independently deliverable chunks with dependency guidance.

When should I use feature decomposition instead of managing the feature as a single work item?▼

Use feature decomposition during early product planning for features spanning multiple components or systems. Managing such features as single work items increases risk, whereas decomposing them into actionable chunks enables parallel work and reduces delivery risk.