execute-outcome

Execute Outcome Work Units in dependency order with isolated Git worktrees.

Updated Jan 21, 2026

Search Tags:#automation #dependencies #linear #execute #git-worktree #outcome #work-units

Ready to run

npx skills add https://github.com/lixxz/claude-workflow --skill execute-outcome

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execute-outcome
Source: https://github.com/lixxz/claude-workflow/tree/main/skills/execute-outcome
Command: npx skills add https://github.com/lixxz/claude-workflow --skill execute-outcome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates and executes all Work Units (sub-issues) for an Outcome, ensuring deterministic integration by honoring dependencies and isolated work environments.

Core Features & Use Cases

Dependency-aware execution: builds a safe order for parallel and sequential Work Units with per-WU isolation.
Git-worktree orchestration: creates and cleans up dedicated worktrees to avoid cross-contamination among WUs.
Automated merge flow: merges completed WUs back into the base branch with conflict handling and human-in-the-loop review.
Use Case: When an Outcome has multiple dependent Tasks, run them in parallel where possible and merge results cleanly, maintaining a reproducible state.

Quick Start

Run the execute-outcome command for a given Outcome ID to begin automated orchestration.

Frequently Asked Questions about execute-outcome

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

FAQPage Schema

How do I execute multiple work units with dependencies in parallel using git worktrees?▼

Dependency-aware execution coordinates parallel and sequential work units by analyzing dependencies and applying topological ordering. It ensures deterministic integration by processing work units only when their dependencies are resolved.

What is the best way to manage automated merges and handle conflicts for isolated worktrees?▼

Automated merge handling merges completed work units back into the base branch with built-in conflict detection. It incorporates human-in-the-loop review to safely resolve any integration conflicts that arise during the merge process.

Can I run dependency-aware execution for outcomes without manual worktree cleanup?▼

Yes, git-worktree orchestration automatically creates dedicated worktrees for per-WU isolation and handles cleanup after execution. This maintains a reproducible state without requiring manual worktree management.

When do I need topological ordering for executing outcome work units?▼

Topological ordering is needed when an outcome contains multiple dependent tasks requiring parallel execution. It builds a safe execution order based on work unit dependencies to ensure deterministic integration.

Does dependency-aware execution work with existing Linear sub-issues and outcome structures?▼

It coordinates and executes all work units defined as sub-issues for a given Outcome ID. The skill processes these work units in a dependency-aware order while maintaining isolated worktree environments for each unit.