prd-command

Analyze PRD input and orchestrate parallel implementation tasks with dependencies.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/msanssouci/opencode --skill prd-command
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-command
Source: https://github.com/msanssouci/opencode/tree/main/skills/prd-command
Command: npx skills add https://github.com/msanssouci/opencode --skill prd-command

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires beads-workflow, prd-planner, build-orchestrator.

What problem does it solve?

PRD-to-implementation workflows can be tedious and error-prone; this Skill automates PRD analysis, task creation, and parallel execution with checkpoints.

Core Features & Use Cases

  • End-to-end PRD analysis and epic/task generation
  • Parallel task orchestration with quality gates
  • Beads-based progress tracking and final reporting
  • Real-world use: a product team drafts a PRD and sees automated task breakdown and implementation plan

Quick Start

First, run /prd with your PRD text to generate tasks and start parallel implementation.

Frequently Asked Questions about prd-command

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

FAQPage Schema
How do I automate PRD analysis and task breakdown for product development?

Automate PRD analysis by running the /prd command with your text input to generate structured epics, beads tasks with dependencies, and a parallel execution plan. This identifies and structures the end-to-end workflow from PRD to implementation.

What is the best way to orchestrate parallel frontend and backend tasks from a PRD?

Orchestrate parallel tasks by generating dependency-aware batches of backend and frontend tasks from your PRD. The workflow coordinates parallel execution using build-orchestrator and applies quality gates between batches to ensure implementation integrity.

Can I use beads-workflow for PRD task planning and progress tracking?

Yes, beads-workflow is integrated directly into the PRD-to-implementation workflow to create beads tasks from PRD input, track progress, and provide final commit reporting. It works with prd-planner to manage task dependencies.

Do I need to manually approve checkpoints during automated PRD implementation?

Checkpoint approval is required during the automated PRD implementation workflow. After analyzing the PRD and creating task plans, the workflow pauses for checkpoint approval before coordinating parallel batches of backend and frontend tasks.

What limitations exist when coordinating multi-agent task planning with prd-planner?

Multi-agent coordination with prd-planner requires the beads-workflow and build-orchestrator dependencies to function. The workflow is designed for structured PRD-to-implementation pipelines and may not suit projects lacking clear epic and task definitions.

Does the PRD-to-implementation workflow support final commit reporting?

Yes, the PRD-to-implementation workflow supports final commit reporting. After completing the parallel task batches and passing quality gates, it generates a final report using beads-based progress tracking to summarize the implementation results.