Break broad goals into 3 to 6 MECE sub-parts with explicit scope boundaries.
npx skills add https://github.com/supertyrelle/pelley --skill decompose-supertyrelle
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
This Skill helps you take a broad, ambiguous goal and turn it into a manageable set of smaller, clearly bounded pieces.
Ask the decompose skill to break down your goal into 3 to 6 bounded sub-parts with clear scope and boundaries.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
maxenkoReview recent code changes to surface bugs and refactoring opportunities.
irahardiantoDecompose software tasks into MECE parallelizable sub-tasks with scope cards.
tyevansDecompose large goals into 3-6 bounded sub-parts with scope boundaries.
Pixel-Process-UGDecompose complex tasks into hierarchical work breakdown structures with dependencies and estimates.
