clear-prd

Clarify product requirements through structured questions and write a Draft or Ready PRD.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/ceasarXuu/AstartesSkills --skill clear-prd-ceasarxuu
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: clear-prd
Source: https://github.com/ceasarXuu/AstartesSkills/tree/main/skills/clear-prd
Command: npx skills add https://github.com/ceasarXuu/AstartesSkills --skill clear-prd-ceasarxuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product requests often arrive vague or incomplete, leading teams to build the wrong thing. This Skill turns an unclear product idea into a reviewed PRD by guiding focused, multi-round clarification before any technical design or implementation begins. ## Core Features & Use Cases - Structured Clarification Rounds: Asks dependency-ordered questions across goal, users, scope, journeys, rules, edge cases, and acceptance criteria, downshifting when answers are partial. - PRD Document Contract: Produces a standardized PRD with status (Draft or Ready for implementation), acceptance criteria, open questions, and a review checklist, respecting existing repository PRD locations. - Confirmed Product Decisions: Maintains a protected table of directly user-confirmed material decisions with stable PD IDs that downstream engineering artifacts can reference as canonical product authority. - Use Case: A stakeholder says "build an internal tool for approving creator payouts." The Skill asks layered questions about approval scope, roles, and exceptions, then writes a PRD recording confirmed decisions and flagging open risks. ## Quick Start Ask the agent to use clear-prd to clarify your product request and write a PRD before implementation begins.

Frequently Asked Questions about clear-prd

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

FAQPage Schema
How do I turn a vague product idea into a PRD?â–¼

Start with the clear-prd clarification workflow: it restates the request, asks dependency-ordered questions in structured rounds, and writes a PRD with goals, scope, user journeys, rules, and acceptance criteria once blocking decisions are resolved.

What should a product requirements document include?â–¼

A PRD should include background and intent, goals and success criteria, users and context, scope, core user journey, interaction design, product rules, edge cases, acceptance criteria, and open questions. This Skill generates exactly that structure with a Draft or Ready status.

How are confirmed product decisions tracked in a PRD?â–¼

Confirmed decisions are recorded in a protected Confirmed Product Decisions table with stable IDs like PD1. Only direct user approval counts as confirmation; agent inference, silence, or a generic continue never promote items into the table.

When should I not use a PRD clarification workflow?â–¼

Skip it for trivial edits, direct bug fixes, pure technical implementation, or when a complete PRD already exists and only engineering execution remains. The Skill is designed for incomplete or layered product logic that needs clarification.

Where does the generated PRD file get saved?â–¼

The Skill preserves the repository's existing PRD location first, then falls back to prd/YYYY-MM-DD-topic.md, appending -v2 or -v3 if the path exists. It can also return the PRD inline when there is no active project folder.