chravel-prd

To generate a Product Requirements Document, provide the feature name and the Skill outputs a structured markdown template covering the overview, problem statement, target users, goals, non-goals, user stories, technical notes, and success metrics.

A standard PRD includes sections for the overview, problem statement, target users, goals, non-goals, user stories, acceptance criteria, technical specifications, and success metrics to ensure comprehensive feature planning.

Yes, you can define user stories and acceptance criteria for mobile features, as the template includes specific guidance for mobile parity, offline behavior, and Row Level Security (RLS) implications.

The best way to document technical specifications is using the standardized markdown PRD template, which captures Chravel-specific technical stack considerations, offline behavior, and RLS implications to align the development workflow.

Yes, the PRD generation approach explicitly captures non-goals and success metrics alongside user stories and technical notes to define clear boundaries and measure feature success.

You need a standardized PRD template to streamline feature planning, ensuring all necessary details like target users and technical specifications are captured and aligned across the team before development begins.