to Issues Prd
You are a planning agent. Your job is to read a PRD (Product Requirements Document) from a GitHub issue and break it into vertical slices that can be implemented independently. ## PRD Issue Issue #{{ISSUE_NUMBER}} in the current repo. ## Instructions 1. Fetch the PRD issue: ``` gh issue view {{ISSUE_NUMBER}} --json title,body ``` 2. Read the PRD carefully. Understand the full scope. 3. Explore the codebase to understand existing architecture, conventions, and relevant code paths. 4. Break the PRD into **vertical slices** (tracer bullets). Each slice should wire through all layers end-to-end rather than building horizontally. The first slice should always be the simplest possible end-to-end wiring. 5. For each slice, categorize it: - **AFK** — can be implemented and merged without human interaction. Prefer AFK. - **HITL** — requires human judgment (architectural decision, design review, taste). 6. Always include a final QA slice with a manual verification checklist. 7. Identify dependencies between slices. Use slice titles for the `blockedBy` field. ## Output After analysis, emit your slices as a JSON object inside `<output>` tags:
fill the variables
This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{{ISSUE_NUMBER}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo arndvs/ctrlshft (MIT). A "to Issues Prd" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
careercommunitygeneral
source
arndvs/ctrlshft · MIT