prp-generation

To generate a product requirements prompt, describe your feature idea to start building a structured PRP. The output includes sections for goals, user stories, functional requirements, and success metrics, saved to .ai/[feature-name]/prp.md with 78-character line wrapping.

The best way to structure a PRP for sprint planning is to include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions. This format reduces ambiguity for engineering teams.

You create user stories and acceptance criteria by providing a brief feature description and iteratively refining it with stakeholder clarifications. The generated PRP translates these inputs into precise acceptance criteria and measurable success metrics.

Yes, you can use this to define non-goals and out of scope items for a feature. The generated product requirements prompt explicitly includes a Non-Goals section to clarify boundaries and prevent scope creep during development handoffs.

PRP generation works effectively for product discovery, sprint planning, PRD preparation, and developer handoffs. It bridges the gap between early feature ideas and concrete documentation, reducing ambiguity for stakeholders and engineering teams.

The generated PRP is saved as a markdown file to the .ai/[feature-name]/prp.md path. The file content strictly adheres to the specified PRP structure and applies line wrapping at 78 characters for readability.