decompose

Break broad goals into 3 to 6 MECE sub-parts with explicit scope boundaries.

Updated Feb 20, 2026

Search Tags:#planning #analysis #repository #scope #breakdown #decompose

Ready to run

npx skills add https://github.com/supertyrelle/pelley --skill decompose-supertyrelle

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you take a broad, ambiguous goal and turn it into a manageable set of smaller, clearly bounded pieces.

Core Features & Use Cases

Scope Clarification: Separates one large topic into distinct work areas so you can reason about it without overlap.
Planning Support: Useful before investigation, analysis, or parallel workstreams when you need an actionable breakdown.
Codebase-Aware Decomposition: Grounds the split in real repository structure so the output reflects what actually exists rather than vague assumptions.

Quick Start

Ask the decompose skill to break down your goal into 3 to 6 bounded sub-parts with clear scope and boundaries.

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 project goal into manageable sub-parts?▼

To break down a large project goal, you decompose it into 3 to 6 bounded sub-parts with clear scope boundaries. This ensures your planning produces mutually exclusive work streams that are easier to tackle independently without overlap.

What is the best way to split a broad investigation topic for parallel analysis?▼

Splitting a broad investigation topic requires creating MECE sub-parts with explicit boundaries. This fan-out workflow approach separates the target into distinct work areas, allowing you to reason about each scope independently for parallel analysis.

How do I scope work streams based on actual repository structure instead of assumptions?▼

Scoping work streams based on repository structure involves discovering the actual file layout using Read, Grep, and Glob operations. This grounds the decomposition in real codebase architecture, ensuring the resulting sub-parts reflect what actually exists.

Can I use scope breakdown for planning mutually exclusive codebase tasks?▼

Yes, you can use scope breakdown for planning mutually exclusive codebase tasks. The process generates 3 to 6 clearly bounded sub-parts with explicit scope definitions, ensuring that parallel work streams do not overlap during investigation or implementation.

When do I need to decompose a task into bounded sub-parts?▼

You need to decompose a task into bounded sub-parts when the goal is too broad to tackle at once or requires mutually exclusive work streams. This is essential before investigation, analysis, or parallel workflows to clarify the scope.

Does scope breakdown work for analyzing ambiguous software engineering goals?▼

Yes, scope breakdown works for analyzing ambiguous software engineering goals by turning a broad topic into a manageable set of smaller pieces. It clarifies the scope by separating the target into distinct, actionable work areas.