exec-impl-plan-ref

Coordinate implementation plan tasks with PROGRESS.json tracking and locking.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/tacogips/git-xnotes --skill exec-impl-plan-ref
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exec-impl-plan-ref
Source: https://github.com/tacogips/git-xnotes/tree/main/.claude/skills/exec-impl-plan-ref
Command: npx skills add https://github.com/tacogips/git-xnotes --skill exec-impl-plan-ref

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges execution plans and real code work by providing task selection, parallelization guidance, progress tracking, and a structured review cycle.

Core Features & Use Cases

  • Task selection: Identifies executable tasks based on dependencies and readiness.
  • Progress tracking: Maintains progress state in PROGRESS.json and per-plan logs, with a locking protocol to prevent race conditions.
  • Review-ready workflow: Orchestrates ts-coding, testing, and ts-review cycles to ensure quality before marking tasks complete.
  • Use Case: When coordinating multiple implementation plans across a repo, run cross-plan task execution and have the system update plan files and progress status automatically.

Quick Start

Start automation with: run /impl-exec-auto to generate executable tasks, then use /impl-exec-specific <plan> <TASK IDs> to execute tasks sequentially. Use the lock protocol as described in the skill to manage PROGRESS.json updates.

Frequently Asked Questions about exec-impl-plan-ref

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

FAQPage Schema
How do I track progress and coordinate tasks across multiple implementation plans?

Plan-driven task execution coordinates multi-plan development workflows by reading PROGRESS.json to identify executable tasks, running them via coding agents, and updating plan files to track progress automatically.

What's the best way to prevent race conditions during parallel task execution?

A PROGRESS.json lock protocol prevents race conditions during parallel task execution by serializing progress state updates, ensuring no concurrent writes corrupt the tracking data across interdependent plans.

How do I execute specific tasks from an implementation plan sequentially?

Use the `/impl-exec-specific <plan> <TASK IDs>` command to execute selected tasks sequentially from a specific plan, ensuring dependencies are resolved before running subsequent tasks.

How does task selection work when implementation tasks have dependencies?

Task selection identifies ready tasks by evaluating dependency readiness and execution constraints from PROGRESS.json, ensuring prior work completes before dependent tasks are queued for execution.

Can I run code reviews and testing cycles automatically within a task execution workflow?

The workflow orchestrates ts-coding, testing, and ts-review cycles automatically, ensuring code quality checks pass before marking tasks complete and updating progress logs.

Do I need a PROGRESS.json file to orchestrate implementation plan execution?

Yes, PROGRESS.json is required as it stores the progress state and task readiness data that the execution workflow reads to select tasks, apply locking protocols, and update completion status.