Convert requirements into structured PRDs for agents

To Prd takes the current conversation and codebase understanding and produces a PRD without interviewing the user - it synthesizes what's already been discussed rather than asking new questions. It requires the project's issue tracker and triage-label vocabulary to already be configured (via /setup-matt-pocock-skills if not), and publishes the finished PRD there with a ready-for-agent triage label applied, needing no further triage step.

Use it when the request matches turning the current conversation into a PRD and publishing it to the project issue tracker. Before writing, it explores the repo if that hasn't already happened, uses the project's own domain glossary vocabulary throughout the document, and respects any ADRs in the area being touched rather than re-litigating settled decisions.

Before writing, it sketches the seams at which the feature will be tested, preferring existing seams to new ones and the highest seam possible - the fewer seams across the codebase, the better, with one as the ideal - checking with the user that the chosen seams match their expectations. The PRD itself follows a fixed template: a Problem Statement and Solution written from the user's perspective, an extensive numbered list of User Stories in the form "As an [actor], I want a [feature], so that [benefit]" covering all aspects of the feature, Implementation Decisions (modules, interfaces, technical clarifications, architectural decisions, schema changes, API contracts) that deliberately excludes file paths or code snippets since they go stale quickly - except a prototype-derived snippet that encodes a decision more precisely than prose can (a state machine, reducer, schema, or type shape), trimmed to just the decision-rich parts rather than a working demo - Testing Decisions (what makes a good test, focused on external behavior not implementation details, plus prior art from similar tests already in the codebase), an Out of Scope section, and Further Notes.

1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending

Publishes directly to the project's configured issue tracker with the ready-for-agent triage label, and cross-references the project's domain glossary and existing ADRs rather than introducing new vocabulary or re-deciding settled architecture questions.

Teams that have already talked through a feature in conversation and want that discussion synthesized straight into a structured, agent-ready PRD - user stories, implementation and testing decisions, and scope boundaries - without a separate requirements-gathering interview.