PRD — Platform / Internal PM

Overview

Draft and validate PRDs for platform and internal products: internal customers, APIs/SLAs, adoption, developer experience.

Example Conversation

You: I need a PRD for our internal API platform. We’re standardising on a single gateway and docs; engineering and data teams are the consumers.

Agent: I’ll use the Platform PRD skill: load best-practices and sections (Internal customers, APIs/SLAs, Adoption & rollout), draft from template, then run validate_prd_structure.

Agent: Created prd-internal-api-platform.md. Validation PASS.

What the Tools Validate

validate_prd_structure checks the PRD for required sections (Overview, Goals, Internal customers, APIs/SLAs, Adoption & rollout, Success metrics, NFRs) and unfilled placeholders. Output: PASS / NEEDS_REVISION / FAIL.

Output Excerpt

Platform PRD (excerpt):

## Internal customers

- **Consumers:** Engineering (5 teams), Data (2 teams)
- **Jobs-to-be-done:** Call internal services via one gateway; discover APIs via docs
- **Pain points today:** Multiple gateways; inconsistent auth and versioning

## APIs / SLAs

- **Capabilities:** Routing, auth, rate limits, logging
- **SLAs:** 99.95% uptime; p99 &lt; 100ms added latency
- **Versioning:** URL path /v1/; 6-month deprecation notice

Getting Started

Add your context (internal consumers, SLAs, adoption plan) to the project workspace, then activate the PRD — Platform / Internal PM skill. The agent will guide you through drafting and validating with validate_prd_structure.