tpo-product-requirements-template

Generates structured product requirements documents with traceable requirements, acceptance criteria, and release gates.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-product-requirements-template-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tpo-product-requirements-template
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/tpo-product-requirements-template
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-product-requirements-template-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a complete, consistent PRD from scratch is slow and error-prone, and missing sections like acceptance criteria, non-functional requirements, or out-of-scope items cause rework during development. This Skill provides a standardized product requirements template for a Technical Product Owner Agent so every requirement is traceable to design, code, and tests. ## Core Features & Use Cases - Full PRD structure: Covers document control, problem statement, success metrics, personas, scope, assumptions, constraints, dependencies, and user flows. - Traceable requirements: Uses ID schemes (FR, NFR, UX, DATA, INT, EPIC, STORY, AC) so every feature links to acceptance criteria and QA checks. - MVP and release planning: Includes roadmap phases, release readiness gates, risk registers, and an AI Developer Agent handoff block. - Use Case: A product owner asks an AI agent to draft a PRD for a new onboarding feature; the agent fills each section, producing a document ready for architecture, sprint planning, and QA review. ## Quick Start Ask the agent to draft a product requirements document for your feature using this template, filling in the problem, scope, functional requirements, and acceptance criteria.

Frequently Asked Questions about tpo-product-requirements-template

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product requirements document with an AI agent?

Provide the agent with your product goal and let it fill the template sections: problem statement, personas, scope, functional and non-functional requirements, and acceptance criteria. Each requirement gets a traceable ID linking it to stories, tests, and release gates.

What sections should a PRD template include?

This template includes document control, product summary, success metrics, users and stakeholders, scope with assumptions and dependencies, user flows, functional and non-functional requirements, backlog structure, MVP roadmap, analytics, risks, and release readiness criteria.

How do I make requirements traceable to tests and code?

Assign every requirement a unique ID such as FR-001 or NFR-002 and link it to acceptance criteria IDs like AC-001. The template's tables connect requirements to epics, user stories, and QA checks so nothing ships untested.

Can this PRD template be used to brief an AI developer agent?

Yes, section 11 provides a handoff block where you insert the product goal, requirement IDs, acceptance criteria, constraints, and out-of-scope items. The developer agent must restate the task, list assumptions and risks, and propose a plan before implementing.

When should I not put implementation details in a PRD?

Keep implementation details out of the PRD unless they are hard constraints such as legal, budget, or platform limits. The template directs technical design decisions into a separate technical specification document referenced in document control.