deliver-plan-tracking-issue

Coordinate end-to-end plan-tracking for issue work items across lifecycle checkpoints.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/graysurf/agent-runtime-kit --skill deliver-plan-tracking-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliver-plan-tracking-issue
Source: https://github.com/graysurf/agent-runtime-kit/tree/main/tests/golden/codex/plugins/dispatch/skills/deliver-plan-tracking-issue/expected
Command: npx skills add https://github.com/graysurf/agent-runtime-kit --skill deliver-plan-tracking-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and coordinating end-to-end plan-tracking for issue work items, ensuring visibility and controlled handoffs across the lifecycle.

Core Features & Use Cases

  • Preflight status checks for continuity and evidence
  • End-to-end workflow from implementation through PR delivery, review, and final handoff
  • Live checkpointing, ledger updates, and non-mutating close-ready handoff
  • Clear ownership boundaries and synthesis of evidence for blockers
  • Handoffs upstream to execute-plan-tracking-issue or create-plan-tracking-issue

Quick Start

Start tracking an issue by provisioning a plan run-state and executing the end-to-end checkpoints to drive delivery.

Frequently Asked Questions about deliver-plan-tracking-issue

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

FAQPage Schema
How do I track an issue work item through the entire delivery lifecycle?▼

Issue plan-tracking coordinates delivery, validation, and handoffs across the full lifecycle from preflight checks and implementation through PR delivery, review, and final close-ready handoff to ensure continuous visibility.

What is a close-ready handoff in issue plan-tracking workflows?▼

A close-ready handoff is a non-mutating final checkpoint that synthesizes evidence and enforces ownership boundaries before transferring the tracked issue work item upstream for closure.

How do I enforce prerequisites like profiles and tool versions before issue implementation?▼

Preflight status checks validate continuity and enforce required profiles, tool versions, and evidence requirements before allowing an issue work item to proceed into the implementation phase.

What happens when a checkpoint fails during PR delivery?▼

Failure-mode handling intercepts failed PR delivery checkpoints, halting the workflow to provide ledger updates and synthesize evidence for blockers before resuming the issue plan-tracking process.

Can I use this plan-tracking workflow for upstream issue creation tasks?▼

Yes, the workflow supports upstream handoffs to execute-plan-tracking-issue or create-plan-tracking-issue, allowing you to pass the close-ready state upstream for further issue lifecycle management.

What's the best way to maintain visibility during issue plan-tracking?▼

Live checkpointing combined with continuous ledger updates maintains real-time visibility and controlled handoffs across all phases of the issue work item delivery lifecycle.