skills.rest
tatargabor
tatargaborCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

decompose

Decompose specification documents into executable orchestration plans with orchestration-plan.json.

Updated Aug 23, 2026
Search Tags:#planning#task management#code generation#orchestration#decomposition#spec analysis
One-click install
npx skills add https://github.com/tatargabor/wt-project-base --skill decompose-tatargabor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decompose
Source: https://github.com/tatargabor/wt-project-base/tree/main/.claude/skills/wt/decompose
Command: npx skills add https://github.com/tatargabor/wt-project-base --skill decompose-tatargabor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex process of breaking down a high-level specification document into a granular, actionable execution plan for code changes, ensuring efficient development and adherence to project conventions.

Core Features & Use Cases

  • Spec Analysis: Intelligently reads and interprets specification documents, prioritizing incomplete tasks.
  • Codebase Exploration: Leverages tools to scan the codebase for existing implementations and identify potential merge hazards.
  • Dependency Mapping: Generates a structured orchestration-plan.json with clear task dependencies and complexity assessments.
  • Use Case: A product manager writes a new feature spec. This Skill analyzes the spec, checks the existing codebase for relevant components, and produces a detailed plan for engineers to implement the feature, including task breakdown, dependencies, and estimated complexity.

Quick Start

Use the decompose skill to create an orchestration plan from the specification document located at 'specs/new-user-auth.md'.

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 specification document into an actionable code change plan?▼

To break down a specification document into an actionable code change plan, this Skill analyzes your spec requirements, explores the existing codebase for context, and generates a structured orchestration-plan.json. This output details specific tasks, dependencies, and complexity assessments for your development workflow.

What is the best way to map task dependencies from a feature spec before coding?▼

Mapping task dependencies from a feature spec is best handled by analyzing the requirements and scanning the codebase for existing implementations. This process produces an orchestration-plan.json file that clearly defines execution order and complexity estimates for your coding tasks.

Can I generate an orchestration plan for software development tasks from a markdown spec?▼

Yes, you can generate an orchestration plan for software development tasks directly from a markdown spec. The Skill reads the specification, recalls relevant project memories, and outputs a structured JSON plan detailing required code changes and dependencies.

Does codebase exploration for merge hazards happen automatically during spec analysis?▼

Codebase exploration for merge hazards does happen automatically during spec analysis. The Skill leverages internal tools to scan your existing codebase, identify relevant components, and check for potential integration conflicts before generating the execution plan.

What format does the orchestration plan use to structure code generation tasks?▼

The orchestration plan uses a structured JSON format to organize code generation tasks. This orchestration-plan.json file outlines granular changes, maps dependencies, and provides complexity assessments to guide the implementation of your specification.

When should I avoid using automated task decomposition for code changes?▼

You should avoid using automated task decomposition when your specification document is incomplete or lacks clear requirements. The Skill prioritizes incomplete tasks during spec analysis, so highly ambiguous specs may result in an inaccurate orchestration-plan.json without sufficient context.

Related Skills

Explore More Software Engineering Skills→
stoodderstoodder
1

propose-spec

Generate proposed specification documents from project context and open a pull request.

Community
Advanced
n0rvynn0rvyn
1

execute-plan

Execute verified implementation plan tasks in deterministic 5-task batches.

Community
Advanced
jacob-dietlejacob-dietle
104

context-gap-analysis

Verify required context before executing tasks by searching codebase and GTM documents.

Community
Intermediate
PiaoxuemoliPiaoxuemoli

writing-plans

Generate detailed implementation plans for software development tasks.

Community
Intermediate