prd-orchestrator

Original：🇨🇳 Chinese

Translated

Parse PRD, determine horizontal splitting strategy, and generate mini-PRD with acceptance criteria. Used when the main coordinator receives the initial PRD or needs to re-split work.

1installs

Sourceblueif16/amazing-claude-code-plugins

Added on2026-02-23

NPX Install

npx skill4agent add blueif16/amazing-claude-code-plugins prd-orchestrator

SKILL.md Content (Chinese)

View Translation Comparison →

PRD Orchestrator

Owner: Main Coordinator Only

Responsibilities

Receive PRD file path (e.g.,
```
docs/prds/reddit-bot.md
```
)
Create project folder structure
Move the original PRD to the project folder
Analyze PRD complexity and decide splitting strategy
Generate meta.yaml and mini-PRD for each section
Generate acceptance criteria and context boundaries for each section

Project Folder Structure

When a PRD is received, create the following structure:

docs/prds/reddit-bot/
├── original.md          # Moved original PRD (not copied)
├── meta.yaml           # Project metadata and progress tracking
└── sections/           # Detailed information for each section
    ├── auth/
    │   ├── mini-prd.md
    │   └── checklist.md
    └── payments/
        ├── mini-prd.md
        └── checklist.md

Important: The original PRD file must be moved (mv) instead of copied to ensure a single source of truth.

Splitting Criteria

Default Behavior: Always create directory structure and sections, even if the PRD is small

Splitting strategies:

Complex PRD: Split into multiple sections
Simple PRD: Create a single section
Regardless of size, the complete project folder structure must be created

Output Format

meta.yaml

yaml

project: reddit-bot
created: 2025-01-15T10:00:00Z
original_prd: ./original.md
status: in_progress  # in_progress | completed | blocked

sections:
  auth:
    status: pending  # pending | in_progress | completed | blocked
    branch: reddit-bot/auth
    progress: "0/4"
    files_created: []

  payments:
    status: pending
    branch: reddit-bot/payments
    progress: "0/5"
    files_created: []

merge_status:
  completed: []
  pending: []
  conflicts: []

sections/{section-id}/mini-prd.md

markdown

# Authentication Module

## Scope
Implement user registration, login, and token management functions.

## Acceptance Criteria
- Users can register using email/password
- JWT token is issued upon login
- Protected routes reject invalid tokens
- Refresh token rotation works properly

## Context Boundaries
**Owns:** src/auth/*, src/middleware/auth.ts
**Reads:** src/config/*, src/types/*
**Forbidden:** src/payments/*, src/ui/*

Completion Process

After orchestration is completed, immediately hand over the meta.yaml path to the execution-manager. The execution-manager will:

Create git worktree and tmux session for each section
Monitor all sections until completion
Automatically call merge-resolver to merge results

The prd-orchestrator is only responsible for planning, not implementing specific functions.