How do I install the Create Github Issues skill?

Run npx skillmds@latest add valorisa/create-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 Create 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 Create 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 Create Github Issues free to use?

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

Who published Create Github Issues?

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

Create Github Issues by valorisa — Agent Skill

Name: Create Github Issues
Author: valorisa

Create Github Issues

Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into GitHub issues.

valorisa Updated Sep 21, 2026

File contents

Create GitHub Issues

Break a plan into independently-grabbable issues using vertical slices (tracer bullets).

The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.

3. Draft vertical slices

Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.

Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.

4. Quiz the user

Present the proposed breakdown as a numbered list. For each slice, show:

Title: short descriptive name
Type: HITL / AFK
Blocked by: which other slices (if any) must complete first
User stories covered: which user stories this addresses (if the source material has them)

Ask the user:

Does the granularity feel right? (too coarse / too fine)
Are the dependency relationships correct?
Should any slices be merged or split further?
Are the correct slices marked as HITL and AFK?

Iterate until the user approves the breakdown.

5. Publish the issues to the issue tracker

For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.

Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.

A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).

What to build

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.

Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.

Acceptance criteria

Criterion 1
Criterion 2
Criterion 3

Blocked by

A reference to the blocking ticket (if any)

Or "None - can start immediately" if no blockers.

Do NOT close or modify any parent issue.

---name: create-github-issuesdescription: Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into GitHub issues.---# Create GitHub IssuesBreak a plan into independently-grabbable issues using vertical slices (tracer bullets).The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.## Process### 1. Gather contextWork from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.### 2. Explore the codebase (optional)If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.### 3. Draft vertical slicesBreak the plan into **tracer bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.<vertical-slice-rules>- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)- A completed slice is demoable or verifiable on its own- Prefer many thin slices over few thick ones</vertical-slice-rules>### 4. Quiz the userPresent the proposed breakdown as a numbered list. For each slice, show:- **Title**: short descriptive name- **Type**: HITL / AFK- **Blocked by**: which other slices (if any) must complete first- **User stories covered**: which user stories this addresses (if the source material has them)Ask the user:- Does the granularity feel right? (too coarse / too fine)- Are the dependency relationships correct?- Should any slices be merged or split further?- Are the correct slices marked as HITL and AFK?Iterate until the user approves the breakdown.### 5. Publish the issues to the issue trackerFor each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.<issue-template>## ParentA reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).## What to buildA concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.## Acceptance criteria- [ ] Criterion 1- [ ] Criterion 2- [ ] Criterion 3## Blocked by- A reference to the blocking ticket (if any)Or "None - can start immediately" if no blockers.</issue-template>Do NOT close or modify any parent issue.

Frequently asked questions