Verified:GitHub

decompose

Decompose feature-driven test suites into atomic tasks with wave-based parallel execution and module stewardship artifacts.

8|1|Updated Mar 22, 2026

Search Tags:#testing #decompose #task-decomposition #atomic-tasks #wave-parallelism #module-stewardship

Ready to run

npx skills add https://github.com/zxdxjtu/harness --skill decompose-zxdxjtu

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose tests into atomic tasks and organize them into a wave-based DAG to accelerate feedback loops and improve reliability by enabling parallel execution and clear ownership.

Core Features & Use Cases

Atomize test suites into discrete tasks with explicit inputs/outputs and completion criteria.
Assign wave-based execution order to maximize parallelism while respecting dependencies.
Generate module stewardship artifacts (AGENT.md, module graph, task documentation) to clarify boundaries and ownership.
Use the resulting plan to drive sprint planning, risk assessment, and automation workflows.

Quick Start

Provide a feature identifier (e.g. F001) to generate a complete decomposition plan and task DAG.

Frequently Asked Questions about decompose

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

FAQPage Schema

How do I decompose tests into atomic tasks for parallel execution?▼

To decompose tests into atomic tasks for parallel execution, you provide a feature identifier to generate a task map. This map groups discrete tasks into a wave-based DAG, preserving dependencies while maximizing parallelism across unit, integration, and end-to-end suites.

What is a wave-based DAG for task decomposition?▼

A wave-based DAG is a directed acyclic graph that groups atomic test tasks into execution waves. It organizes tasks so that independent ones run in parallel within the same wave, while strictly respecting dependency boundaries to accelerate feedback loops.

How do I generate module stewardship artifacts for test decomposition?▼

You generate module stewardship artifacts by analyzing feature-driven tests and creating an AGENT.md file per module. This process also builds a module-graph and compiles a tasks document to clarify ownership boundaries and track sprint progress.

Can I use task decomposition for unit, integration, and end-to-end test suites?▼

Yes, task decomposition applies to feature-driven test suites across unit, integration, and end-to-end levels. It atomizes these tests into discrete tasks with explicit inputs, outputs, and completion criteria to drive sprint planning and automation workflows.

What is the best way to track progress for decomposed test tasks?▼

The best way to track progress for decomposed test tasks is to compile a comprehensive tasks document. This document maps the atomic tasks, wave-based execution order, and module stewardship boundaries generated during the decomposition process.

Does test decomposition work without external dependencies?▼

Yes, test decomposition works without external dependencies. You simply provide a feature identifier like F001 to generate a complete decomposition plan and task DAG, organizing tests into atomic tasks with clear inputs and outputs.