ralph-tui-prd

To generate a structured PRD for AI feature development, provide a concise feature description and desired outcomes. The skill interactively clarifies requirements through guided questions and outputs a finalized PRD wrapped in [PRD] markers for easy ingestion.

A product requirements document for AI workflows should include sections for overview, quality gates, user stories, functional requirements, non-goals, technical considerations, success metrics, and open questions. This ensures comprehensive scope definition and machine-verifiable acceptance criteria.

Yes, you can automate PRD creation within a TUI environment. This skill produces a ready-to-save Markdown artifact formatted with frontmatter-driven names, designed specifically for Ralph TUI ingestion and saving to ./tasks/prd-<feature-name>.md.

AI-assisted interactive clarification works by guiding users through targeted questions to refine requirements and scope. This iterative process eliminates ambiguity in informal feature ideas, accelerating the translation into formal, review-ready PRDs.

The best way to format machine-verifiable acceptance criteria in a PRD is by using frontmatter-driven names and structured Markdown. This skill adheres to strict project formatting conventions, ensuring the generated artifact is ready for automated validation.

Automated PRD generation for complex feature planning requires clear initial inputs and relies on iterative clarification to define scope. It focuses on structuring provided ideas rather than inventing requirements, meaning poorly defined feature concepts may still yield ambiguous non-goals or open questions.