vibe-prd

The vibe-prd skill acts as a structured product management assistant within the vibe-coding ecosystem, specifically designed to bridge the gap between initial ideation and technical execution. It facilitates the creation of a comprehensive Product Requirements Document (PRD) by walking the user through a guided, step-by-step interview process that adapts based on the user's technical background—whether they are a non-technical 'vibe-coder,' an experienced developer, or somewhere in between.

This skill ensures continuity by checking for existing research files (such as research-*.md) and referencing them to inform the PRD, effectively anchoring the requirements in previous validation steps. It prompts users to define critical aspects of their MVP, including core problems, user personas, user journeys, Must-Have features (using MoSCoW prioritization for developers), and success metrics. Once all information is gathered, the agent generates a structured markdown file named docs/PRD-[AppName]-MVP.md, which serves as the source of truth for the subsequent technical design and build phases.

• Automatically checks for and integrates prior research insights from local project files.

• Supports tailored workflows for different technical levels: Vibe-coder, Developer, and In-between.

• Ensures high-quality output through a 'Verification Echo' phase that summarizes the product scope for final approval.

• Generates a professional, structured PRD covering overview, user journeys, MVP feature sets, design direction, and technical constraints.

• Guides the user through a defined roadmap to ensure the PRD is ready for the technical design phase (vibe-techdesign).

• Requires the project to have a consistent structure for docs/ and research files.

• Best used after the initial market research phase to ensure the PRD is grounded in user needs.

• Operates best when the user provides honest assessments of their technical background to receive the appropriate depth of questioning.

• Designed for the vibe-coding workflow; encourages the use of model family names rather than specific version pins to maintain flexibility.

• Ideal for MVPs and early-stage startup projects where clarity, scope definition, and rapid, consistent documentation are essential.