prd

To generate a Product Requirements Document, use this skill to answer targeted clarifying questions about your feature. It then structures your input into standard PRD sections like Goals, User Stories, and Functional Requirements, saving the completed document to a specified task file.

A standard PRD for software development should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and acceptance criteria. This skill automatically structures your project scope details into these specific sections for clear developer alignment.

Yes, you can use this tool to gather project requirements and write user stories. It prompts you with targeted questions to extract necessary feature planning details, ensuring your user stories and functional requirements are clearly defined before generating the final document.

The best way to document project scope and non-goals is through a structured PRD. This skill guides you through defining explicit boundaries and feature requirements, outputting a comprehensive document that ensures alignment across your product management and development teams.

Yes, this PRD generator asks targeted clarifying questions before creating the document. It collects necessary information about your feature planning and user stories to ensure the final product requirements document accurately defines your project scope.

To save a generated PRD, the skill automatically writes the structured document containing your functional requirements and user stories to a specified task file. This ensures your product management documentation is stored and ready for developer reference.