From aaf3050857a8d00c710c382c87a29b81341370aa Mon Sep 17 00:00:00 2001 From: Test Date: Fri, 17 Apr 2026 13:10:02 +0100 Subject: [PATCH] Updated write-a-prd to to-prd --- {prd-to-issues => to-issues}/SKILL.md | 33 ++++++++++----------------- {write-a-prd => to-prd}/SKILL.md | 16 ++++++------- 2 files changed, 19 insertions(+), 30 deletions(-) rename {prd-to-issues => to-issues}/SKILL.md (61%) rename {write-a-prd => to-prd}/SKILL.md (65%) diff --git a/prd-to-issues/SKILL.md b/to-issues/SKILL.md similarity index 61% rename from prd-to-issues/SKILL.md rename to to-issues/SKILL.md index 893a56f..50597e0 100644 --- a/prd-to-issues/SKILL.md +++ b/to-issues/SKILL.md @@ -1,19 +1,17 @@ --- -name: prd-to-issues -description: Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items. +name: to-issues +description: 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 issues. --- -# PRD to Issues +# To Issues -Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets). +Break a plan into independently-grabbable GitHub issues using vertical slices (tracer bullets). ## Process -### 1. Locate the PRD +### 1. Gather context -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 ` (with comments). +Work from whatever is already in the conversation context. If the user passes a GitHub issue number or URL as an argument, fetch it with `gh issue view ` (with comments). ### 2. Explore the codebase (optional) @@ -21,7 +19,7 @@ If you have not already explored the codebase, do so to understand the current s ### 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. +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. @@ -38,7 +36,7 @@ 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 +- **User stories covered**: which user stories this addresses (if the source material has them) Ask the user: @@ -56,13 +54,13 @@ For each approved slice, create a GitHub issue using `gh issue create`. Use the Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field. -## Parent PRD +## Parent -# +# (if the source was a GitHub 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. Reference specific sections of the parent PRD rather than duplicating content. +A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation. ## Acceptance criteria @@ -76,13 +74,6 @@ A concise description of this vertical slice. Describe the end-to-end behavior, Or "None - can start immediately" if no blockers. -## User stories addressed - -Reference by number from the parent PRD: - -- User story 3 -- User story 7 - -Do NOT close or modify the parent PRD issue. +Do NOT close or modify any parent issue. diff --git a/write-a-prd/SKILL.md b/to-prd/SKILL.md similarity index 65% rename from write-a-prd/SKILL.md rename to to-prd/SKILL.md index 8cf6eab..269fd48 100644 --- a/write-a-prd/SKILL.md +++ b/to-prd/SKILL.md @@ -1,23 +1,21 @@ --- -name: write-a-prd -description: Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature. +name: to-prd +description: Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context. --- -This skill will be invoked when the user wants to create a PRD. You may skip steps if you don't consider them necessary. +This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know. -1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions. +## Process -2. Explore the repo to verify their assertions and understand the current state of the codebase. +1. Explore the repo to understand the current state of the codebase, if you haven't already. -3. Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. - -4. Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation. +2. Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation. A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes. Check with the user that these modules match their expectations. Check with the user which modules they want tests written for. -5. Once you have a complete understanding of the problem and solution, use the template below to write the PRD. The PRD should be submitted as a GitHub issue. +3. Write the PRD using the template below and submit it as a GitHub issue.