Agent skill · product strategy · sundial-org
prd
Create and manage Product Requirements Documents (PRDs). Use when: (1) Creating structured task lists with user stories, (2) Specifying features with acceptance criteria, (3) Planning feature implementation for AI agents or human developers.
Why this skill is useful
Provides a structured format for defining user stories and acceptance criteria that enhances feature planning for AI agents and developers.
What it needs
About 2k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.
What this skill does
PRD Skill Create and manage Product Requirements Documents (PRDs) for feature planning. What is a PRD? A PRD (Product Requirements Document) is a structured specification that: 1. Breaks a feature into small, independent user stories 2. Defines verifiable acceptance criteria for each story 3. Orders tasks by dependency (schema → backend → UI) Quick Start 1. Create/edit agents/prd.json in the project 2. Define user stories with acceptance criteria 3. Track progress by updating passes: false → true prd.json Format Field Descriptions Field Description ------- ------------- project Project name for context branchName Git branch for this feature (prefix with ralph/) description One-line feature summary userStories List of stories to complete userStories[].id Unique identifier (US-001, US-002) userStories[].title Short descriptive title userStories[].description "As a [user], I want [feature] so that [benefit]" userStories[].acceptanceCriteria Verifiable checklist items userStories[].priority Execution order (1 = first) userStories[].passes Completion status (false → true when done) userStories[].notes Runtime notes added by agent Story Sizing Each story should be completable in one context window. ✅ Right-sized: Add a database column and migration Add a UI component to an existing page Update a server action with new logic Add a filter dropdown to a list ❌ Too large (split these): "Build the entire dashboard" → Split into: schema, queries, UI, filters "Add authentication" → Split into: schema, middleware, login UI, session Story Ordering Stories execute in priority order. Earlier stories must NOT depend on later ones. Correct order: 1. Schema/database changes (migrations) 2. Server actions / backend logic 3. UI components that use the backend 4. Dashboard/summary views Acceptance Criteria Must be verifiable, not vague. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sundial-org/prd