WA
Write a PRD Skills: High-Quality Requirement Document Generator
mattpocock
2026-04-06

When product managers use openclaw/hermes agent for requirement planning, write-a-prd skills can reverse-explore existing codebases and automatically generate technical PRDs, seamlessly bridging product and R&D communication.

Introduction

The write-a-prd skill helps developers draft Product Requirements Documents (PRDs) through a structured interview and exploration process. In actual development, vague requirements often lead to extensive rework later in the development cycle. This skill forces the AI to act as a requirements analyst, confirming details, checking the existing codebase, and planning module interfaces before any code is written, ensuring the feature is actually viable.

Concept

Eliminate ambiguity before coding through relentless questioning, codebase exploration, and deep module design, ultimately outputting the final result as a standardized GitHub Issue.

Setup and Usage

There are several ways to install the skill:

  • Method 1: In the OpenClaw or Hermes Agent chat window, directly tell the Agent: “Please help me install the write-a-prd skill.” (Easiest)
  • Method 2: Visit the skillhub website, install the skillhub store first, and then install the corresponding skill. (For Chinese users)
  • Method 3: Visit the Skills.sh website, search for the skill name on the homepage, and use the provided command to install it. (For technical users)
  • Method 4: Visit the Clawhub website, search for the skill name on the homepage, click the download button to get the zip file, extract it, and place it in the skills directory of OpenClaw.

Skill Workflow Analysis

  • Requirement Gathering: Asks the user for a detailed description of the problem and potential solutions.
  • Codebase Exploration: Scans the existing repository to verify the user’s assumptions and ensure compatibility with the current architecture.
  • Relentless Questioning: Interviews the user continuously on plan details, walking down design branches to resolve dependency conflicts early.
  • Deep Module Design: Outlines core module structures before drafting the PRD. It actively identifies “deep modules” (complex internal logic with simple interfaces) that are easy to test in isolation, and confirms the testing scope with the user.
  • Templated Output: Once aligned, it generates a PRD using a strict template (covering Problem, Solution, User Stories, Implementation & Testing Decisions, and Out of Scope) and submits it directly as a GitHub Issue.

Skill Evaluation

SKILL.md

Back to Product Manager Skills List