prd▌

Convert product requirements into independently-deliverable GitHub issues using vertical-slice architecture. \n \n Fetches PRD content from GitHub, analyzes the codebase context, and breaks requirements into thin vertical slices that span all integration layers end-to-end \n Distinguishes between HITL (human-in-the-loop, requiring decisions) and AFK (autonomous, mergeable without review) slices, preferring AFK where possible \n Presents proposed breakdown for user feedback on granularity, depend

Collaborative PRD creation through structured interviews, codebase analysis, and modular design planning. \n \n Guides users through problem definition, solution ideation, and iterative design interviews to reach shared understanding \n Explores the codebase to validate assumptions and understand current architecture before planning changes \n Designs modular solutions by identifying deep modules with simple, testable interfaces that encapsulate significant functionality \n Generates comprehensi

This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.

Convert a PRD into a phased implementation plan using vertical-slice tracer bullets. \n \n Breaks down product requirements into thin, end-to-end slices that cut through all integration layers (schema, API, UI, tests) rather than horizontal layers \n Identifies and documents durable architectural decisions upfront (routes, schema, data models, auth boundaries) so all phases reference consistent foundations \n Outputs a structured Markdown plan file in ./plans/ with phases, user story mappings, a

Turn the current conversation context into a PRD and submit it as a GitHub issue.

Structured Product Requirements Documents that align stakeholders and guide development teams. \n \n Guides discovery through targeted questions to gather problem statement, user personas, business goals, success metrics, and timeline before document generation \n Generates comprehensive PRDs using industry-standard templates covering executive summary, problem statement, user stories, success metrics, scope, technical considerations, risks, and dependencies \n Supports multiple PRD formats: sta

Structured PRD generation prompt for breaking down Epics into detailed feature specifications. \n \n Generates complete Product Requirements Documents in markdown format with standardized sections covering goals, user personas, stories, functional and non-functional requirements, and acceptance criteria \n Prompts for clarifying questions when insufficient information is provided, ensuring comprehensive feature definition before engineering handoff \n Organizes output into a consistent file stru

prd-mastery:-context-aware

Perform a short PRD precheck, present issues and questions, then implement only after the user confirms or adjusts the PRD.

A PRD creation skill that uses persistent file-based planning to maintain coherent thinking and avoid "left-brain vs right-brain" context switching issues.