prd-skill20260303Create and manage Product Requirements Documents by defining user stories with acceptance criteria, ordering tasks by dependencies, and tracking progress.
Install via ClawdBot CLI:
clawdbot install zhao202404/prd-skill20260303Grade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/snarktank/ralphAudited Apr 17, 2026 · audit v1.0
Generated Oct 27, 2026
Engineering teams use this skill to convert a feature request into a dependency-ordered prd.json of small user stories with verifiable acceptance criteria. AI coding agents (Claude Code, OpenCode) then execute stories in priority order and flip passes to true as each completes.
Product managers and tech leads break epics into right-sized stories with acceptance criteria before sprint planning. The priority field and schema-to-UI ordering ensure work is sequenced correctly and progress is trackable via simple jq queries.
Solo developers building apps with AI assistants use the PRD format to keep agent work scoped to one context window per story. Runtime notes capture implementation decisions like migration strategies for later review.
Operations teams specifying internal features (admin dashboards, filter dropdowns) use prd.json as a lightweight spec and status tracker. Git branch naming with the ralph/ prefix ties each PRD to its feature branch for clean PR workflow.
Instructors teach structured agentic development by having students write PRDs with acceptance criteria and completion flags. The verifiable checklist pattern reinforces testable requirement writing before code generation.
The skill is distributed freely to grow adoption across AI coding agent ecosystems, with the prd.json format becoming a de facto standard for agent task specs.
Bundled as a feature in a paid AI coding assistant or agent orchestration platform, letting customers spec and execute staged feature work from within the product.
Agencies and internal platform teams adopt the PRD skill as part of standardizing agent-assisted delivery, with services around process design, story sizing, and CI integration.
💬 Integration Tip
Save the PRD at agents/prd.json and standardize queries like jq '.userStories[] | select(.passes == false)' in project docs or CI so agents and humans share one progress view. Always include 'Typecheck passes' in acceptance criteria to keep generated work verifiable.
Scored Jun 29, 2026
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking....
The meta-framework for how a company runs — the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native,...
生成收钱吧生意贷(含消费贷)产品的完整 PRD(产品需求文档)。严格按 PRD 模板(项目基础信息→概述→流程→功能详情→非功能→验收标准)、统一埋点事件(LoanPageDisplay/LoanPageClick/LoanUIViewDisplay)规范输出。触发词:「请根据 [PRD 规范] 为我输出:[业务...
Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusabl...
Atlassian Administrator for managing and organizing Atlassian products (Jira, Confluence, Bitbucket, Trello), users, permissions, security, integrations, sys...
Cross-functional what-if modeling for cascading multi-variable scenarios. Unlike single-assumption stress testing, this models compound adversity across all...