From github-workflow
Saves the latest implementation plan from docs/plans/ to a GitHub issue with repo, branch, and directory context for execution in a separate Claude Code session.
npx claudepluginhub dapi/claude-code-marketplace --plugin github-workflowThis skill is limited to using the following tools:
Save an implementation plan as a GitHub issue for execution in a separate Claude Code session.
Creates GitHub issues for each phase of an implementation plan using feature_request.yml or chore_request.yml templates. Checks existing issues before creating or updating.
Captures brainstormed solutions from conversation as pre-planned GitHub issues with Implementation Plan sections (Context, Exploration, Risks, Approach, Dependency Graph, Tasks) for fast-tracking planning.
Creates structured GitHub issues with implementation plans from task descriptions by analyzing docs, designs, and code. Updates existing issues by number using gh CLI.
Share bugs, ideas, or general feedback.
Save an implementation plan as a GitHub issue for execution in a separate Claude Code session.
Announce at start: "Saving implementation plan to GitHub issue."
Search from the git repository root:
REPO_ROOT=$(git rev-parse --show-toplevel)
ls -t "$REPO_ROOT"/docs/plans/*.md 2>/dev/null | head -1
If no plan files found, check if user specified a file path. If still nothing, report error: "No plan files found in docs/plans/. Please specify the plan file path."
Read the plan file content using the Read tool.
Run these commands to get repository and branch info:
# Repository (owner/repo format)
gh repo view --json nameWithOwner -q .nameWithOwner
# Current branch
git branch --show-current
# Working directory
pwd
Structure the issue body as follows:
> **For Claude:** Use `superpowers:executing-plans` skill to implement this plan task-by-task.
> Start in the worktree directory shown below.
**Context**
| Field | Value |
|-------|-------|
| Repository | {owner/repo} |
| Branch | {branch-name} |
| Working directory | {pwd} |
| Plan file | {relative path to plan file} |
---
{Full plan file content}
Parse the first # heading from the plan file as the issue title.
If no heading found, use the filename (without date prefix and extension).
Use --body-file - to handle large plans (avoids command-line length limits):
echo "$BODY" | gh issue create --title "{title}" --body-file - --label "plan"
If the "plan" label does not exist, create without labels:
echo "$BODY" | gh issue create --title "{title}" --body-file -
Show the created issue URL and suggest how to use it:
"Plan saved to {issue_url}
To execute in a separate session:
gh auth loginecho "$BODY" | gh issue create --body-file - to preserve formattingsuperpowers:executing-plans reference so the next session knows what skill to use