skills.rest
hylarucoder
hylarucoderCOMMUNITY
Explore all skills by this author →
Website𝕏@hylarucoderGitHub

hai-prd

Define and refine product requirements by drafting and auditing PRDs.

278|15|Updated Mar 25, 2026
Search Tags:#requirements#product management#acceptance criteria#product design#prd#scope analysis
One-click install
npx skills add https://github.com/hylarucoder/hai-stack --skill hai-prd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hai-prd
Source: https://github.com/hylarucoder/hai-stack/tree/main/skills/hai-prd
Command: npx skills add https://github.com/hylarucoder/hai-stack --skill hai-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents unclear product requirements, oversized PRDs, and untestable acceptance criteria by helping teams decide when a PRD is needed and ensuring the document represents a focused product argument.

Core Features & Use Cases

  • PRD Decision Support: Determines whether a request needs a PRD or a different artifact such as a goal document, design document, or task note.
  • PRD Creation and Refinement: Drafts product requirements from problems, audits existing PRDs for drift, and repairs unclear goals, scope, behavior, and acceptance criteria.
  • Scope Management: Evaluates whether PRDs should be split, merged, or kept together using user journey, value, acceptance, and boundary tests.

Quick Start

Use the hai-prd skill to review this feature idea and decide whether it needs a PRD, then draft the right requirements document.

Frequently Asked Questions about hai-prd

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

FAQPage Schema
How do I write a product requirement document with clear scope and testable acceptance criteria?▼

Draft a product requirement document by analyzing product boundaries, mapping user journeys, and defining testable acceptance criteria to ensure requirement consistency. This prevents oversized PRDs and untestable conditions.

Do I always need a PRD for every new feature request?▼

You do not always need a PRD for every feature request. PRD decision support evaluates whether a request requires a full product requirement document or a different artifact like a goal document, design document, or task note.

How do I audit an existing PRD for scope drift and unclear goals?▼

Audit an existing PRD by reviewing it for drift, then repairing unclear goals, scope, behavior, and acceptance criteria. This refinement ensures the document represents a focused product argument with consistent boundaries.

When should I split or merge product requirement documents?▼

Split or merge product requirement documents by applying user journey, value, acceptance, and boundary tests. This scope management evaluation determines whether PRDs should remain together or be divided to maintain focus.

What is the best way to define product boundaries and user journeys for requirements?▼

The best way to define product boundaries and user journeys is through structured analysis of the product scope. This shapes the product requirements into a clear argument, preventing unclear requests and ensuring behavior aligns with value.

Related Skills

Explore More Product & Management Skills→
HerbertJulioHerbertJulio
20

prd

Translate product ideas into structured PRDs with user stories and GitHub issues.

Community
Advanced
drvossdrvoss
42

product-capability

Translate product requirements into testable capability specifications with acceptance criteria and traceability.

Community
Intermediate
lucabattistinilucabattistini

design-flows

Map user journeys with happy paths, error states, and branching logic.

Community
Intermediate
dhaneshdhanesh
8

manifold-m-quick

Automate lightweight three-phase code change workflows for bug fixes and small features.

Community
Intermediate