executing-plans

Execute sequential epic tasks with STOP checkpoints using TaskList and TaskGet APIs.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Veraticus/gambit --skill executing-plans-veraticus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/Veraticus/gambit/tree/main/skills/executing-plans
Command: npx skills add https://github.com/Veraticus/gambit --skill executing-plans-veraticus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a disciplined, one-task-at-a-time execution model with mandatory human checkpoints.

Core Features & Use Cases

  • One-task-at-a-time execution: Run a single task, review results, and STOP before proceeding.
  • Epic-driven work: Load immutable epic requirements and align every task to success criteria.
  • Checkpoint-driven workflow: STOP after each task to gather learnings and replan if needed.
  • Use case: Manage a multi-step epic by executing tasks sequentially with mandatory reviews to ensure quality and traceability.

Quick Start

Start a run with /gambit:execute-plan, then follow prompts to pick the next ready task, mark it in_progress, complete steps, verify, and STOP. After reviewing the checkpoint, run /gambit:execute-plan again to proceed with the next task.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I execute epic tasks one at a time with mandatory review checkpoints?

To execute epic tasks one at a time with checkpoints, you load immutable epic requirements, mark a task in_progress, verify completion, and STOP for user review before running the workflow command again to proceed to the next task.

What is a checkpoint-driven workflow for multi-subtask epics?

A checkpoint-driven workflow for multi-subtask epics is a sequential execution model where tasks run one at a time and STOP after completion to gather learnings, replan if needed, and present a summary for mandatory human intervention before proceeding.

How do I manage task state and verify completion during sequential workflow execution?

Managing task state during sequential workflow execution relies on TaskList, TaskGet, and TaskUpdate operations to track progress, verify completion, and update task statuses. The workflow marks tasks in_progress, verifies them upon completion, and STOPs for checkpoint review.

Can I use sequential task execution for multi-step software development epics?

Yes, you can use sequential task execution for multi-step software development epics. The workflow applies specifically to multi-subtask epics in software development, executing tasks sequentially and requiring review at each checkpoint before continuing to the next task.

When should I not use a one-task-at-a-time execution model?

You should not use a one-task-at-a-time execution model when tasks can run in parallel or when mandatory human checkpoints between tasks would disrupt your workflow. It is designed for multi-subtask epics requiring sequential execution, quality review, and traceability before proceeding.