prd-planner

Name: prd-planner
Availability: InStock
Author: Zhao

Persist PRD thinking across four files and generate PRD and technical design documents.

69|11|Updated Jan 10, 2026

Search Tags:#workflow #planning #architecture #documentation #requirements #prd #technical-design

Ready to run

npx skills add https://github.com/zhaono1/agent-playbook --skill prd-planner-zhaono1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-planner
Source: https://github.com/zhaono1/agent-playbook/tree/main/skills/prd-planner
Command: npx skills add https://github.com/zhaono1/agent-playbook --skill prd-planner-zhaono1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PRD creation often suffers from context loss as requirements, research, and design ideas are scattered across documents and memory.

Core Features & Use Cases

Four-file pattern (docs/{scope}-prd-notes.md, docs/{scope}-prd-task-plan.md, docs/{scope}-prd.md, docs/{scope}-tech.md) to persist thinking and keep context intact.
Guided workflow for gathering requirements, research, architecture options, and synthesis into PRD and technical design.
Auto-tracking and traceability: notes and plans update as phases complete, with options compared for architecture decisions.
Use Case: A product team drafts a PRD for a new feature, records findings, assesses options, and outputs both PRD and tech design documents.

Quick Start

Instruct the agent to initialize a new PRD project and generate the four files, then begin gathering requirements.

Frequently Asked Questions about prd-planner

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

FAQPage Schema

How do I structure PRD creation to avoid losing context across research and technical design?▼

To avoid context loss during PRD creation, use a four-file workflow that persists thinking through notes, task plans, PRDs, and technical design documents. This pattern keeps requirements, research, and architecture decisions intact and traceable.

What is the best way to document architecture options when planning a new product feature?▼

The best way to document architecture options is using a guided workflow that compares options within technical design artifacts. Updating notes and task plans as phases complete ensures architecture decisions are evaluated and traced back to requirements.

How do I generate both a PRD and a technical design document from initial requirements?▼

Generate both PRD and technical design documents by initializing a four-file pattern workflow. Instruct the agent to gather requirements, record findings, assess architecture options, and synthesize the outputs into final PRD and tech files.

Can I track PRD task progress automatically as requirements gathering phases complete?▼

Yes, you can track PRD task progress through auto-tracking within the file-based workflow. As phases complete, the notes and task plan files update automatically, maintaining traceability across the requirements and design synthesis process.

Does this PRD workflow require any external dependencies or specific platforms?▼

No, this PRD workflow requires no external dependencies. It operates entirely through a file-based pattern, persisting context locally in markdown files for notes, task plans, PRDs, and technical design without needing third-party integrations.