Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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.
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.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Create and manage Product Requirements Documents (PRDs) for feature planning.
A PRD (Product Requirements Document) is a structured specification that: Breaks a feature into small, independent user stories Defines verifiable acceptance criteria for each story Orders tasks by dependency (schema โ backend โ UI)
Create/edit agents/prd.json in the project Define user stories with acceptance criteria Track progress by updating passes: false โ true
{ "project": "MyApp", "branchName": "ralph/feature-name", "description": "Short description of the feature", "userStories": [ { "id": "US-001", "title": "Add priority field to database", "description": "As a developer, I need to store task priority.", "acceptanceCriteria": [ "Add priority column: 'high' | 'medium' | 'low'", "Generate and run migration", "Typecheck passes" ], "priority": 1, "passes": false, "notes": "" } ] }
FieldDescriptionprojectProject name for contextbranchNameGit branch for this feature (prefix with ralph/)descriptionOne-line feature summaryuserStoriesList of stories to completeuserStories[].idUnique identifier (US-001, US-002)userStories[].titleShort descriptive titleuserStories[].description"As a [user], I want [feature] so that [benefit]"userStories[].acceptanceCriteriaVerifiable checklist itemsuserStories[].priorityExecution order (1 = first)userStories[].passesCompletion status (false โ true when done)userStories[].notesRuntime notes added by agent
Each story should be completable in one context window.
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
"Build the entire dashboard" โ Split into: schema, queries, UI, filters "Add authentication" โ Split into: schema, middleware, login UI, session
Stories execute in priority order. Earlier stories must NOT depend on later ones. Correct order: Schema/database changes (migrations) Server actions / backend logic UI components that use the backend Dashboard/summary views
Must be verifiable, not vague.
"Add status column to tasks table with default 'pending'" "Filter dropdown has options: All, Active, Completed" "Typecheck passes"
"Works correctly" "User can do X easily" Always include: "Typecheck passes"
Update passes: true when a story is complete. Use notes field for runtime observations: "notes": "Used IF NOT EXISTS for migrations"
ActionCommandCreate PRDSave to agents/prd.jsonCheck status`cat prd.jsonView incomplete`jq '.userStories[]
See references/ for detailed documentation: agent-usage.md - How AI agents execute PRDs (Claude Code, OpenCode, etc.) workflows.md - Sequential workflow patterns output-patterns.md - Templates and examples
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.