execute-task

Implements planned tasks autonomously using coordinator-subagent phases, worktrees, and pull requests.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill execute-task-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute-task
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/execute-task
Command: npx skills add https://github.com/mistakenot/skills --skill execute-task-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a written implementation plan into working code requires coordinating many steps—reading task docs, isolating work, executing phases in order, tracking progress, and opening a PR—which is error-prone when done manually or in a single unstructured agent session. ## Core Features & Use Cases - Coordinator-Subagent Execution: Dispatches one subagent per plan phase, following the Execution Sequence DAG from plan.md, with serial or parallel execution as the DAG allows. - Isolated Worktree Workflow: Creates a git worktree with branch task/$ID-$NAME so implementation never touches the main planning branch. - Progress Tracking & Resumption: Updates plan.md checkboxes and commits after each phase, so an interrupted session resumes from the first unchecked phase. - Use Case: After committing planning docs for task 042, run the skill with the task ID; it reads the plan, executes each phase via subagents, marks the task complete, and opens a PR with a structured body. ## Quick Start Execute task 042 by reading its planning docs and implementing each phase in an isolated worktree, then open a pull request.

Frequently Asked Questions about execute-task

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

FAQPage Schema
How do I execute a planned task with AI subagents?▼

Provide the numeric task ID; the skill finds the matching folder under docs/tasks/, reads the plan, creates a worktree, and dispatches one subagent per phase. Each subagent reports status, files changed, and verification results back to the coordinator.

How does the coordinator-subagent pattern work for code implementation?▼

The coordinator parses plan.md phases and dispatches subagents with absolute worktree paths, since subagents do not inherit the coordinator's working directory. After each phase, the coordinator checks off plan items, commits progress, and decides whether to continue, fix, or stop.

Can I resume an interrupted task execution session?▼

Yes, session resumption is built in. A new session reads plan.md and resumes from the first unchecked phase, since completed phases are marked with checked boxes and committed after each subagent finishes.

What happens when a subagent fails during task execution?▼

Subagents fix routine failures like test bugs, type errors, and lint issues autonomously. The coordinator attempts resolution for routine failures it receives, but stops on fundamental issues like wrong architecture and still opens a PR documenting what happened.

What are the prerequisites for running task execution?▼

All four planning docs must exist in the task folder: requirements.md, solution.md, context.md, and plan.md. There must be no unanswered open questions, and every acceptance criterion must be covered by plan steps.