publish-plan

Commit plan artifacts to a branch, open a draft PR, and comment on the issue.

5|Updated Jul 25, 2025

Search Tags:#git #workflow #planning #publish #plan #pr #issue-tracking

Ready to run

npx skills add https://github.com/tomzx/agents --skill publish-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish-plan
Source: https://github.com/tomzx/agents/tree/main/skills/publish-plan
Command: npx skills add https://github.com/tomzx/agents --skill publish-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically turns a reviewed implementation plan into a tracked, auditable artifact by committing plan materials to a dedicated branch, opening a draft PR, and notifying the issue author.

Core Features & Use Cases

Commit plan artifacts to a dedicated branch named plan/<issue-number>.
Open a draft PR linked to the originating issue and describe the plan in the PR.
Post a comment on the issue to notify stakeholders that the plan is ready for review.
Use Case: When a feature is being planned, run /publish-plan <issue> to publish the plan and surface next steps to the team.

Quick Start

Run /publish-plan <issue-url-or-number> to publish the plan for review by creating the plan branch, opening a draft PR, and commenting on the issue.

Frequently Asked Questions about publish-plan

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

FAQPage Schema

How do I publish an implementation plan as a draft PR on GitHub?▼

To publish a plan via draft PR, run /publish-plan <issue> to commit plan artifacts to a dedicated branch, open a draft PR linked to the issue, and notify stakeholders through a comment.

How do I notify stakeholders that a feature plan is ready for review?▼

Publishing a plan via draft PR automatically posts a comment on the originating issue to notify stakeholders that the plan is ready for review before development begins.

Do I need the gh CLI to create a plan branch and draft PR?▼

Yes, you need the gh CLI installed and GitHub repository access to automate branch creation, draft PR opening, and issue notification.

What is the best way to track an implementation plan before coding starts?▼

The best way to track an implementation plan is committing it to a dedicated branch named plan/<issue-number> and opening a linked draft PR to create an auditable artifact.

Can I use publish-plan for issue tracking workflows without a formal plan file?▼

No, you need a plan file available for publishing, as the workflow requires committing plan materials to a branch and describing the plan in the draft PR.

Why does publish-plan create a dedicated branch instead of committing directly?▼

Creating a dedicated branch named plan/<issue-number> isolates plan materials, turns them into a tracked code change, and enables formal review through a linked draft PR.