prd

Capture product requirements into structured PRD documents with acceptance checklists.

15|1|Updated Mar 29, 2026

Search Tags:#planning #documentation #requirements #prd #acceptance #kickoff

Ready to run

npx skills add https://github.com/duronext/jig --skill prd-duronext

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/duronext/jig/tree/main/core/skills/prd
Command: npx skills add https://github.com/duronext/jig --skill prd-duronext

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designed to reduce ambiguity and misalignment in product work by enabling teams to collaboratively author structured PRDs that serve as enforceable specifications for both humans and downstream AI agents.

Core Features & Use Cases

Structured PRD templates for Full PRD (12 sections) and Light PRD (5 sections) to fit project scope.
Guided workflow: Step-by-step prompts during REQUIREMENTS and BRAINSTORM phases that surface decisions.
Lifecycle integration: Saved outputs to docs/plans with ticket-system sync and acceptance checklists.
Cross-team collaboration: Reuse PRDs across API, data, logic, and UI.

Quick Start

Ask me to generate a PRD for a feature or bug, and I will create a structured document ready for kickoff.

Frequently Asked Questions about prd

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

FAQPage Schema

How do I write a product requirements document for a new feature kickoff?▼

To write a product requirements document, use guided step-by-step prompts to capture API, data, logic, and UI considerations. This generates a structured PRD file saved as docs/plans/YYYY-MM-DD-<topic>-prd.md, ready for collaborative kickoff.

What is the difference between a full PRD and a light PRD?▼

A full PRD contains 12 sections for comprehensive feature planning, while a light PRD contains 5 sections for smaller scope tasks or bugs. Both generate structured requirements documents with an acceptance checklist for downstream reviewers.

Can I create a structured PRD for bug fixes and smaller tasks?▼

Yes, you can create a structured PRD for bug fixes by selecting the 5-section light PRD template. It formalizes bug requirements and saves the output to docs/plans with an integrated acceptance checklist for reviewers.

How do I formalize brainstorming decisions into enforceable specifications?▼

Formalize brainstorming decisions by applying guided prompts during the requirements phase to surface choices across API, data, logic, and UI. This reduces ambiguity and outputs enforceable specifications for humans and AI agents.

Does generating a PRD automatically include an acceptance checklist for reviewers?▼

Yes, generating a PRD automatically includes an acceptance checklist integrated for downstream reviewers. This ensures the saved requirements document serves as an enforceable specification for both human and AI agent validation.

What is the best way to align cross-team product requirements for API and UI work?▼

The best way to align cross-team product requirements is to author a collaborative PRD covering API, data, logic, and UI considerations. This structured document reduces misalignment and syncs with ticket systems for downstream use.