execution-workflow

name	execution-workflow
description	Use when an approved delivery slice or plan exists and the next step is execution, or when debugging, TDD, E2E acceptance, parallel task coordination, or isolated workspace setup is needed (approved slice, approved plan, coordinated execution, implementation execution, worktree, isolated workspace, branch isolation, plan execution, TDD, test first, failing test, bugfix, regression proof, E2E, end-to-end, acceptance test, test suite, acceptance gate, parallel agents, subagent, independent task, coordinator, debugging, root cause, unexpected behavior, verification failure).
argument-hint	Target, e.g.: implementation-checklist.md slice 1, full plan run, worktree setup for plan/20260320-p0, debug routing regression, TDD for validation helper, run E2E acceptance for checkout service, parallelize 3 independent verification tasks
user-invocable	true

Execution Workflow

Covers implementation execution, isolated workspace setup, test-driven development, E2E testing and acceptance, parallel agent coordination, and systematic debugging — the full execution phase after planning is complete.

Module Routing

Identify the task, then load only the matching module via read_file before proceeding.

Task	Module
Execute one approved slice or a full approved multi-slice plan	modules/implementation.md
Set up an isolated branch and worktree before execution starts	modules/worktrees.md
Feature or bugfix changes code behavior and a test harness is available	modules/tdd.md
Two or more independent tasks can run in parallel without shared file or slice-order dependencies	modules/parallel-agents.md
Run full E2E, integration, or acceptance test suites with automated triage and acceptance gating	modules/e2e-acceptance.md
Tests fail, behavior is unexpected, or a change is blocked by unknown root cause	modules/debugging.md

Load exactly one module, then follow its Procedure section.

Typical Flow

(optional) worktrees  →  implementation  →  tdd (inside slice)
                                ↓
                          e2e-acceptance  (plan-level or tranche-level acceptance)
                          debugging  (when verification fails)
                          parallel-agents  (when independent support tasks surface)

When Not to Use This Skill

• Design, contracts, or evidence are not yet stable → use design-workflow first
• Scope still needs to be split into slices → use planning-workflow first
• Documents need to be moved, renamed, or archived → use document-lifecycle-workflow