PRD — Technical Product Manager

Overview

Draft and validate PRDs for technical products: APIs, integrations, infra, NFRs, feasibility.

Example Conversation

You: I need a PRD for our new public API. We’re exposing our core workflow as REST; we need versioning and rate limits.

Agent: I’ll use the Technical PRD skill: load best-practices and sections checklist, draft Technical scope, APIs/integrations, NFRs, and Feasibility, then run validate_prd_structure.

Agent: Created prd-public-api.md. Running validate_prd_structure… PASS.

What the Tools Validate

validate_prd_structure checks the PRD for required sections (Overview, Goals, Technical scope, APIs/integrations, NFRs, Feasibility & risks, Success metrics) and unfilled placeholders. Output: PASS when no errors and no placeholders; NEEDS_REVISION when only warnings; FAIL when sections are missing.

Output Excerpt

Technical PRD (excerpt):

## APIs / integrations

- **APIs:** REST v1; resource-based URLs; JSON. Version prefix /v1/
- **Integrations:** None for v1; webhooks in v2 scope
- **Versioning:** Semantic; 12-month deprecation for major

## Non-functional requirements

- **Performance:** p99 &lt; 200ms for read; 500ms for write
- **Availability:** 99.9% SLA
- **Rate limits:** 1000 req/min per API key; 429 + Retry-After

Getting Started

Add your context (APIs, NFRs, feasibility notes) to the project workspace, then activate the PRD — Technical Product Manager skill. The agent will guide you through drafting and validating with validate_prd_structure.