orchestrator-planner

Generates structured JSON planning documents for Claude Orchestrator tasks.

29|3|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/parallax-ai-llc/claude-orchestrator --skill orchestrator-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-planner
Source: https://github.com/parallax-ai-llc/claude-orchestrator/tree/main/src/skills/orchestrator-planner
Command: npx skills add https://github.com/parallax-ai-llc/claude-orchestrator --skill orchestrator-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product planners craft a clear vision, define features, user flows, and technical requirements to guide the orchestration process.

Core Features & Use Cases

  • Product Vision: Define the core value proposition and success metrics.
  • Feature Definition: Break down requirements with acceptance criteria.
  • User Flow Design: Map journeys and identify pain points.

Quick Start

Create a planning document outlining product vision, core features with acceptance criteria, and key user flows for the orchestrator.

Frequently Asked Questions about orchestrator-planner

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

FAQPage Schema
How do I create a structured planning document for product development?

A planning document organizes product vision, core features with acceptance criteria, user flows, and technical requirements into a JSON payload. This Skill generates that structure automatically, capturing taskId, platform, timestamp, and all planning fields to guide orchestration and keep stakeholders aligned.

What should I include when defining product features and user flows?

Feature definitions need acceptance criteria that clarify scope and success. User flows map customer journeys and identify pain points. This Skill structures both into a planning document, validating completeness so your orchestration process has clear, testable requirements and user experience blueprints.

Can I use this to document technical requirements alongside product vision?

Yes. The planning document includes fields for product vision, core features, user flows, and technical requirements in one JSON output. This consolidates planning artifacts so technical teams and product stakeholders work from the same validated source during orchestration.

How does this Skill handle incomplete or missing planning information?

The Skill validates planning completeness and handles edge cases within the JSON payload generation. It flags gaps in vision, features, flows, or requirements so you can address them before passing the document to orchestration tasks.

What format does the planning document output use?

The output is a JSON planning_document payload with structured fields: taskId, platform, timestamp, productVision, coreFeatures, userFlows, and requirements. This format integrates directly with Claude Orchestrator tasks for consistent downstream processing.

Related Skills