Prd To Issues

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementa...

Security Scan

The skill's instructions clearly act on GitHub (using the gh CLI to read and create issues) but the package metadata does not declare the gh binary or any GitHub credential requirements, which is an incoherence you should resolve before installing.

Purpose & Capability

The skill's stated purpose is to convert a PRD into GitHub issues, and the SKILL.md explicitly instructs running `gh issue view` and `gh issue create`. However, the registry metadata declares no required binaries and no credentials. A coherent skill would declare the gh CLI (or an API token) as required and/or document how authentication should be provided.

Instruction Scope

The runtime instructions stay within the expected scope: locate the PRD (via gh), optionally explore the codebase, draft vertical-slice issues, ask the user to approve, and create issues with `gh issue create`. It does not instruct reading unrelated files or exfiltrating data. It does assume the agent can run gh against the target repository.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an installer. That minimizes risk; the primary runtime action is invoking the user's gh CLI.

Credentials

The skill requires access to GitHub via `gh` but declares no required env vars or primary credential. In practice `gh` will need a logged-in user or a GH token (GH_TOKEN or gh auth). The absence of declared credentials is an omission that hides the fact that the agent will need permission to create issues in repositories.

Persistence & Privilege

always is false and the skill does not request permanent presence or modify other skills. Autonomous invocation (model invocation enabled) is the default platform behavior; the skill could create issues when invoked, but it does not demand elevated platform privileges itself.

What to consider before installing

Before installing: (1) confirm that you are comfortable with the agent running the GitHub CLI (gh) — it will fetch PRD issues and create new issues in your repo. (2) Ask the publisher to update metadata to declare the gh binary and to document required authentication (e.g., GH_TOKEN or gh auth login). (3) Run the skill first in a test repository or with a limited-permission account. (4) If you enable autonomous invocation, be aware the agent could create issues without additional prompts; restrict its GitHub permissions accordingly.

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

Process

1. Locate the PRD

Ask the user for the PRD GitHub issue number (or URL).

If the PRD is not already in your context window, fetch it with gh issue view <number> (with comments).

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code.

3. Draft vertical slices

Break the PRD 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 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 from the PRD this addresses

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. Create the GitHub issues

For each approved slice, create a GitHub issue using gh issue create. Use the issue body template below.

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

<issue-template> ## Parent PRD

#<prd-issue-number>

What to build

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation. Reference specific sections of the parent PRD rather than duplicating content.

Acceptance criteria

• Criterion 1
• Criterion 2
• Criterion 3

Blocked by

• Blocked by #<issue-number> (if any)

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

User stories addressed

Reference by number from the parent PRD:

• User story 3
• User story 7

</issue-template>

Do NOT close or modify the parent PRD issue.