execplan

Manage living ExecPlans within GitHub issue comments.

2|Updated Feb 23, 2026

Search Tags:#automation #developer tools #issue tracking #github issues #workflow management #execplan

Ready to run

npx skills add https://github.com/vultuk/coding-agents --skill execplan-vultuk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execplan
Source: https://github.com/vultuk/coding-agents/tree/main/skills/execplan
Command: npx skills add https://github.com/vultuk/coding-agents --skill execplan-vultuk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms GitHub issues into dynamic, executable plans managed directly within issue comments, eliminating the need for separate local markdown files and ensuring plans stay synchronized with ongoing work.

Core Features & Use Cases

Issue-backed Plans: Creates and maintains a single, authoritative ExecPlan within a GitHub issue comment.
Automated Workflow Management: Handles claiming issues, updating plans in place, and executing steps with progress tracking.
Use Case: When you need to implement a feature described in a GitHub issue, use this Skill to create a living plan in the issue's comments, track progress there, and ensure all work is documented and traceable.

Quick Start

Use the execplan skill to create a living ExecPlan for issue #123.

Frequently Asked Questions about execplan

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

FAQPage Schema

How do I manage executable development plans directly within GitHub issues?▼

Automating GitHub issue workflow management handles claiming issues, updating plans in place, and tracking progress directly within issue comments. This eliminates separate local markdown files by keeping plans synchronized with ongoing work in the thread.

Do I need the gh CLI to track GitHub issue progress in comments?▼

Yes, `gh` CLI authentication is required to manipulate GitHub issues and comments. This dependency enables the automated claiming of issues, plan updates, and progress tracking directly within the issue thread.

What is the best way to keep feature implementation plans synchronized with ongoing GitHub work?▼

Using GitHub issues as a living ExecPlan ensures plans stay synchronized with ongoing work. It transforms issue comments into an authoritative, executable specification, maintaining a single source of truth for development tasks and tracking progress.

Can I automate claiming GitHub issues and updating plans in place?▼

Yes, automating issue claiming and plan updates is a core feature. It handles these workflow management tasks directly in the GitHub issue thread, ensuring plans are updated in place and progress is tracked automatically.

Why use GitHub issue comments for living plans instead of local markdown files?▼

GitHub issue comments provide a single source of truth, eliminating separate local markdown files. This ensures the plan stays synchronized with ongoing work, creating a self-contained, executable specification directly where development happens.