What it is
to-prd is a skill for turning conversation context into a product requirements document. Its source guidance also covers publishing or handing the result to an issue tracker.
Why it is useful
Agent conversations often contain decisions, constraints, and open questions that never become a durable spec. This skill captures them before implementation starts.
Best uses
- Convert a long product discussion into a PRD.
- Prepare a feature spec before breaking it into tickets.
- Record assumptions, scope, non-goals, and acceptance criteria.
Notes
A PRD should stay editable. Use this skill to create the first durable draft, then review it with the people who own product and implementation.