decompose

Decompose large goals into 3-6 bounded sub-parts with scope boundaries.

14|6|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/tyevans/tackline --skill decompose-tyevans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decompose
Source: https://github.com/tyevans/tackline/tree/main/skills/core/decompose
Command: npx skills add https://github.com/tyevans/tackline --skill decompose-tyevans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of tackling overly large or vague goals by systematically breaking them down into smaller, more manageable sub-parts with clearly defined scopes.

Core Features & Use Cases

  • Goal Decomposition: Splits complex objectives into 3-6 distinct, bounded sub-parts.
  • Scope Definition: Clearly defines what is included (scope) and excluded (boundary) for each sub-part.
  • Isolation Assessment: Determines if sub-parts are independent (disjoint file sets) or shared-state (overlapping files), guiding parallelization strategies.
  • Use Case: Before starting a large feature development, use decompose to identify distinct modules like "user authentication," "data storage," and "API endpoints," each with its own clear boundaries.

Quick Start

Use the decompose skill to break down the goal of implementing a new user profile page.

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 feature into manageable sub-parts?

Task breakdown uses file pattern overlap to identify independent or shared-state isolation for each sub-part. This grounds the decomposition in actual codebase structure, clearly defining what is included and excluded for each module.

What is bounded context in task decomposition for software engineering?

Bounded context in task decomposition defines clear scope boundaries for each sub-part, specifying exactly what is included and excluded. It identifies independent or shared-state isolation to guide parallelization strategies based on file pattern overlap.

How do I plan parallel development workflows for complex goals?

Plan parallel development workflows by decomposing complex goals into 3-6 bounded sub-parts and assessing their isolation. The breakdown determines if sub-parts are independent disjoint file sets or share overlapping files to guide your strategy.

When should I subdivide a project before starting feature development?

Subdivide a project before starting feature development when facing overly large or vague goals. Breaking the objective into bounded sub-parts with clear scope boundaries prevents ambiguity and ensures systematic module isolation.