orchestrator-planner

Generate JSON planning documents with product vision, features, user flows, and requirements.

Updated Nov 19, 2025
One-click install
npx skills add https://github.com/Fire-ants-never-die/PB.ai_Web --skill orchestrator-planner-fire-ants-never-die
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-planner
Source: https://github.com/Fire-ants-never-die/PB.ai_Web/tree/main/.claude/skills/orchestrator-planner
Command: npx skills add https://github.com/Fire-ants-never-die/PB.ai_Web --skill orchestrator-planner-fire-ants-never-die

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product Planner for Claude Orchestrator. Creates planning documents with product vision, features, user flows, and requirements.

Core Features & Use Cases

  • Product Vision: Define the core value proposition, target users, and brand identity.
  • Feature Definition: Break down requirements into concrete features with acceptance criteria.
  • User Flow Design: Map key user journeys and identify opportunities for improvement.
  • Requirements Analysis: Gather technical requirements and success metrics.

Quick Start

Provide a product vision and 2-3 features; output a planning document outlining the vision, features, user flows, and requirements.

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 product planning document with vision, features, and requirements?

Product planning documents combine vision statements, feature definitions with acceptance criteria, user flows, and technical requirements into a structured JSON output. Define your core value proposition and 2-3 key features; the planner generates a complete planning document mapping user journeys and success metrics for orchestrator projects.

What should I include in a product vision statement?

Product vision articulates core value proposition, identifies target users, and establishes brand identity. This foundation guides feature prioritization and user flow design, ensuring features align with strategic direction and user needs throughout the planning document.

How do I define acceptance criteria for product features?

Acceptance criteria specify measurable outcomes that validate feature completion. The planner breaks requirements into concrete features paired with acceptance criteria, enabling stakeholders to verify features meet user needs and technical specifications before implementation.

Can I map user journeys and identify improvement opportunities in product planning?

User flow design maps key user journeys through your product and highlights optimization opportunities. The planner generates structured user flows that reveal pain points and areas for enhancement, informing feature prioritization and requirements refinement.

What's the difference between product planning and requirements gathering?

Product planning integrates vision, features, and user flows into a holistic strategy, while requirements gathering focuses narrowly on technical specifications. The planner combines both, producing comprehensive planning outputs with vision, feature acceptance criteria, user flows, and measurable requirements.

Who should contribute to product planning for stakeholder alignment?

Product planning involves product managers, engineers, designers, and stakeholder input on vision and roadmap. The planner structures collaboration by organizing product vision, features, user flows, and technical requirements into a shared planning document that aligns cross-functional teams.