How do I install the Plan To Github Issues skill?

Run npx skillmds@latest add rockclaver/plan-to-github-issues in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plan To Github Issues safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plan To Github Issues?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plan To Github Issues free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Plan To Github Issues?

rockclaver (@rockclaver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plan To Github Issues by rockclaver

Name: Plan To Github Issues
Author: rockclaver

Plan To Github Issues

Convert a phased plan into GitHub issues, a CI workflow, and a PR template mapping PRs to criteria. Use when user wants to create issues from a plan, push phases to GitHub, set up acceptance-criteria CI, or track plan phases.

rockclaver f6b1264 2.1 KB Updated Sep 17, 2026

File contents

Plan to GitHub Issues

1. Locate the plan

Find **/plans/plan-*.md or ask. Repo: gh repo view --json nameWithOwner. Each ## Phase N: Title + - [ ] criteria.

2. Create labels

gh label create "phase" --color "#0052CC" --description "Implementation phase" --repo OWNER/REPO
gh label create "acceptance-criteria" --color "#5319E7" --description "Has acceptance criteria" --repo OWNER/REPO

3. Create one issue per phase

Title: Phase N: <Title>, labels phase/enhancement/acceptance-criteria, run in parallel.

Overview

<"What to build" content from the plan phase> Related user stories:

Acceptance Criteria

Test Coverage Requirements

Every checkbox needs a validating test; PR is blocked unless CI passes.

4. Create the CI workflow

Create .github/workflows/ci.yml via the Contents API:

On PR (open/sync/reopen) + push to main
Real Postgres+Redis containers, no mocks
deps → typecheck → migrate → test w/ coverage → upload artifact
acceptance-criteria-check job (PR-only): counts - [ ] via Closes #N, warns only
Lint job; adapt commands per package.json/bunfig.toml

gh api --method PUT /repos/OWNER/REPO/contents/.github/workflows/ci.yml \
  -f message="chore: add CI workflow with acceptance criteria tracking" \
  -f content="<base64>"

5. Create the PR template

Create .github/PULL_REQUEST_TEMPLATE.md (same API): Closes #N field, criteria checklist, criterion→test table, merge checklist.

6. Report back

List issue URLs, confirm paths. PRs add Closes #N; check criteria as proven; CI warns on unchecked.

Notes

Create issues in parallel. No checkout → Contents API for files. No overview → use title + criteria. Fake secrets only.

---name: plan-to-github-issuesdescription: Convert a phased plan into GitHub issues, a CI workflow, and a PR template mapping PRs to criteria. Use when user wants to create issues from a plan, push phases to GitHub, set up acceptance-criteria CI, or track plan phases.---# Plan to GitHub Issues### 1. Locate the planFind `**/plans/plan-*.md` or ask. Repo: `gh repo view --json nameWithOwner`. Each `## Phase N: Title` + `- [ ]` criteria.### 2. Create labels```bashgh label create "phase" --color "#0052CC" --description "Implementation phase" --repo OWNER/REPOgh label create "acceptance-criteria" --color "#5319E7" --description "Has acceptance criteria" --repo OWNER/REPO```### 3. Create one issue per phaseTitle: `Phase N: <Title>`, labels `phase`/`enhancement`/`acceptance-criteria`, run in parallel.<issue-body-template>## Overview<"What to build" content from the plan phase>**Related user stories**: <user stories list from the plan>## Acceptance Criteria<acceptance criteria checklist copied verbatim from the plan, as - [ ] items>## Test Coverage RequirementsEvery checkbox needs a validating test; PR is blocked unless CI passes.</issue-body-template>### 4. Create the CI workflowCreate `.github/workflows/ci.yml` via the Contents API:- On PR (open/sync/reopen) + push to `main`- Real Postgres+Redis containers, no mocks- deps → typecheck → migrate → test w/ coverage → upload artifact- `acceptance-criteria-check` job (PR-only): counts `- [ ]` via `Closes #N`, warns only- Lint job; adapt commands per `package.json`/`bunfig.toml````bashgh api --method PUT /repos/OWNER/REPO/contents/.github/workflows/ci.yml \ -f message="chore: add CI workflow with acceptance criteria tracking" \ -f content="<base64>"```### 5. Create the PR templateCreate `.github/PULL_REQUEST_TEMPLATE.md` (same API): `Closes #N` field, criteria checklist, criterion→test table, merge checklist.### 6. Report backList issue URLs, confirm paths. PRs add `Closes #N`; check criteria as proven; CI warns on unchecked.## NotesCreate issues in parallel. No checkout → Contents API for files. No overview → use title + criteria. Fake secrets only.

Frequently asked questions