execute-task

Automate TASK-NNN execution with worktree isolation, TDD cycles, validation, and merging.

41|4|Updated Jan 28, 2026

Search Tags:#tdd #validation #worktree #merge #task-management #execute

Ready to run

npx skills add https://github.com/etr/groundwork --skill execute-task-etr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execute-task
Source: https://github.com/etr/groundwork/tree/main/skills/execute-task
Command: npx skills add https://github.com/etr/groundwork --skill execute-task-etr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the complete workflow to execute a TASK-NNN, including worktree isolation, TDD cycles, validation, and merging, so humans can focus on higher-level planning.

Core Features & Use Cases

Worktree isolation for task-specific development
TDD-driven implementation with incremental verification
Automated validation across quality, security, and architecture checks
Automated merge and status tracking with clear progress reporting
Plan-driven execution with guardrails to prevent scope drift

Quick Start

Invoke the execute-task skill to run a TASK-NNN workflow from planning through validation and merge.

Frequently Asked Questions about execute-task

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

FAQPage Schema

How do I automate task execution with TDD cycles and worktree isolation?▼

Automating task execution with TDD cycles and worktree isolation is handled by coordinating a plan-driven workflow that isolates task-specific development, runs incremental verification, and enforces guardrails to prevent scope drift.

How does worktree isolation work for task-specific development in a monorepo?▼

Worktree isolation for task-specific development works by creating a separate branch environment for TASK-NNN execution, applicable to both single-project and monorepo environments, ensuring clean validation and automated merging.

What is the best way to enforce a plan-driven workflow with guardrails to prevent scope drift?▼

Enforcing a plan-driven workflow with guardrails prevents scope drift by automating the end-to-end execution of a TASK-NNN, applying strict boundaries around task specs, and providing structured status updates and final outcomes.

Can I use automated validation across quality, security, and architecture checks before merging?▼

Automated validation across quality, security, and architecture checks before merging is supported by the execute-task workflow, running these checks incrementally during the TDD cycle to ensure code meets all criteria prior to the automated merge.

Does automated task execution provide structured status updates and final outcomes?▼

Automated task execution provides structured status updates and final outcomes by coordinating the workflow from planning through validation and merge, tracking progress reporting so humans can focus on higher-level planning.

When should I not use an automated end-to-end task execution workflow?▼

You should not use an automated end-to-end task execution workflow when tasks lack clearly defined task specs, as the orchestration relies on plan-driven execution with guardrails to properly coordinate worktree isolation, TDD cycles, validation, and merging.