publish-plan

Publish Plan

Commits the implementation plan produced by /create-plan to a dedicated branch, opens a draft PR linked to the originating issue, and posts a comment on the issue so the author knows a plan is ready for their review.

Prerequisites

• Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
• If no argument is provided, target the issue from $ISSUE_NUMBER (and $REPO).
• gh CLI authenticated with write access to the repository
• A reviewed plan file in context or at $2 (defaults to .sdlc/features/N-<slug>/plan.md; falls back to plan.md in the working directory)
• Issue URL or number ($1)
• Clean or committable working tree

Skill attribution (GitHub)

Before posting the issue comment with gh, read github-post-attribution/SKILL.md and append the Posted with footer for SKILL_DIR = publish-plan.

Because publish-plan always runs within the sdlc pipeline, include the SDLC phase footer described in github-post-attribution/SKILL.md (prepend the SDLC phase: plan (<FEAT-id> #<issue>) line above the Posted with line).

Workflow

Read plan file ($2 or plan.md)
           |
           v
Create branch: plan/<issue-number>
           |
           v
Commit plan file
           |
           v
Push branch
           |
           v
Open draft PR (linked to issue)
           |
           v
Post comment on issue (links to PR)

Steps

1. Resolve the issue number from $1:

   ghx issue view $1
   

   Extract the issue number and repository (owner/repo).

2. Determine the plan file path: use $2 if provided, otherwise look for .sdlc/features/N-<slug>/plan.md (where <feature> matches the issue number), then fall back to plan.md in the current directory. Stop and inform the user if no plan file is found.

3. Create and switch to a plan branch:

   git checkout -b plan/<issue-number>
   

4. Stage and commit the .sdlc/features/N-<slug>/ directory (which contains requirements, specification, and plan artifacts):

   git add .sdlc/features/N-<slug>/
   git commit -m "docs: add implementation plan for #<issue-number>"