prd-to-issues

Included with Lifetime

$97 forever

Break a PRD, plan, or spec into independently-grabbable GitHub issues using tracer-bullet vertical slices, classified HITL vs AFK with dependency ordering. Use when the user wants to convert a plan into issues, create implementation tickets, or break work into issues.

General

What this skill does


# PRD → Issues

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

If the user passed an issue reference, file path, or PRD path as an argument, fetch and read it fully
(body + comments).

## Process

### 1. Gather context

Work from whatever is already in the conversation. Otherwise find the PRD — read the given path or
check `docs/plans/`. If none exists, suggest `/tt:write-prd`.

### 2. Get repo and labels

- `gh repo view --json nameWithOwner --jq '.nameWithOwner'`
- `gh label list --json name --jq '.[].name'` — discover the real label vocabulary.

If you have not explored the codebase yet, do so. Issue titles/descriptions should use the project's
domain glossary (`CONTEXT.md`) vocabulary and respect decision issues in the area.

### 3. Draft vertical slices (tracer bullets)

Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end — NOT a
horizontal slice of one layer.

- 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; riskiest unknowns early.

**Classify each slice HITL or AFK:**

- **HITL** — requires human interaction (an architectural decision, a design review, manual testing).
- **AFK** — can be implemented and merged without human interaction.

Prefer AFK over HITL where possible.

### 4. Quiz the user

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

- **Title** — short descriptive name
- **Type** — HITL / AFK
- **Blocked by** — which slices must complete first
- **User stories covered** — which stories this addresses (if the source has them)

Ask: Does the granularity feel right (too coarse / too fine)? Are the dependencies correct? Should any
slices merge or split? Are HITL/AFK marked correctly? Iterate until approved.

### 5. Create the issues

Publish in **dependency order** (blockers first) so you can reference real issue numbers in "Blocked
by". Use `gh issue create` with:

- Title prefix: `feat:`, `fix:`, `refactor:`, `chore:`
- Real repo labels (from step 2). For **AFK** slices, apply the `ready-for-agent` label if it exists
  (map the canonical name to the repo's actual label; ask if unclear).
- The body template below.

Do NOT close or modify any parent issue.

### 6. Report

A table with issue URLs and the dependency graph.

## Issue Body Template

```markdown
## Parent

Reference to the parent issue (omit if the source wasn't an existing issue).

## What to build

A concise description of this vertical slice — the end-to-end behavior, not layer-by-layer
implementation. Avoid file paths and code snippets (they go stale). Exception: a prototype-produced
snippet that encodes a decision precisely (state machine, reducer, schema, type shape) may be inlined,
trimmed, and noted as prototype-sourced.

## Acceptance Criteria

- [ ] Criterion 1
- [ ] Criterion 2

## Blocked by

- #N (or "None — can start immediately")
```

## Rules

- Vertical slices, not horizontal layers.
- Each issue completable in a single session.
- Riskiest slices first.
- Prefer AFK over HITL.

Files: 1

Size: 3.5 KB

Complexity: 13/100

Category: General

Source: https://github.com/christowles/towles-tool/tree/main/packages/core/skills/prd-to-issues

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts