prd▌

You are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.

Generate detailed Product Requirements Documents optimized for AI agent execution via ralph-tui task orchestration. \n \n Guides users through adaptive clarifying questions to understand feature scope, goals, and quality requirements \n Produces structured PRDs with user stories, functional requirements, and explicit quality gates for automated conversion to beads issues or prd.json \n Emphasizes small, independently completable user stories with verifiable acceptance criteria suitable for singl

Structured PRD creation from discovery notes to engineering-ready requirements document. \n \n Orchestrates 8 phases across 2–4 days: problem framing, persona definition, strategic context, solution overview, success metrics, user stories, and scope/dependencies documentation \n Includes problem statement with evidence, target personas, business goals, and competitive context to align stakeholders before engineering begins \n Breaks solutions into epic hypotheses and user stories with acceptance

Template-based PRD authoring, format validation, and GitHub PR submission guidance for Day 6. \n \n Guides participants through environment checks (git, gh CLI, repo access), GitHub ID confirmation, and PRD creation or validation in under 15 minutes \n Provides a structured PRD template covering problem definition, skills inventory, and change history; validates eight required sections before submission \n Automates git workflow (branch creation, commit, push) and opens a GitHub PR with a single

Transform a rough product idea into a comprehensive, AI-ready Product Requirements Document (PDF) through targeted questions and structured output.

Generate comprehensive Product Requirements Documents that translate business vision into technical specifications. \n \n Follows a strict three-phase workflow: discovery interview to fill knowledge gaps, analysis and scoping to identify dependencies, and technical drafting using a standardized PRD schema \n Requires concrete, measurable success criteria and acceptance criteria; explicitly avoids vague language like \"fast\" or \"intuitive\" in favor of quantifiable benchmarks \n Covers executiv

Generate structured Product Requirements Documents from feature descriptions with clarifying questions. \n \n Asks 3–5 targeted clarifying questions with lettered options to resolve ambiguity before drafting \n Produces a complete PRD with user stories, functional requirements, acceptance criteria, and success metrics \n Saves output to tasks/prd-[feature-name].md in markdown format, ready for implementation handoff \n Designed for junior developers and AI agents: explicit, unambiguous, with con