orchestrator-planner

Generate structured planning documents in a defined JSON schema for Claude Orchestrator projects.

Updated Nov 28, 2025
One-click install
npx skills add https://github.com/JunHyuk-Kang/ai-co-learner --skill orchestrator-planner-junhyuk-kang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-planner
Source: https://github.com/JunHyuk-Kang/ai-co-learner/tree/main/.claude/skills/orchestrator-planner
Command: npx skills add https://github.com/JunHyuk-Kang/ai-co-learner --skill orchestrator-planner-junhyuk-kang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A Product Planner defines product vision, features, user flows, and requirements to guide the orchestrator's development efforts.

Core Features & Use Cases

  • Product vision & identity: Articulate the core value proposition and brand voice.
  • Feature definitions: Break down needs into concrete features with acceptance criteria.
  • User flows: Map key journeys and identify pain points.

Quick Start

Draft a planning document outlining the product vision, core features with acceptance criteria, and 1-2 user flows for the next release.

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 features and user flows?

A planning document articulates product vision, breaks features into concrete definitions with acceptance criteria, and maps user flows to guide development. This Skill generates a formal JSON schema artifact with taskId, platform, productVision, coreFeatures, userFlows, and requirements fields, ensuring cohesive planning for orchestrator projects.

What should a product planning document include for feature rollouts?

Effective planning documents define core value proposition, decompose needs into features with measurable acceptance criteria, and trace key user journeys to identify pain points. This Skill structures these elements into a standardized output format aligned with orchestrator project requirements.

Can I use planning documents to define technical requirements alongside product vision?

Yes. Planning documents capture both product vision and technical requirements in a unified schema. This Skill outputs formal artifacts combining productVision, coreFeatures, userFlows, and requirements fields to guide orchestrator development with functional and technical clarity.

How do I break down product needs into features with acceptance criteria?

Feature definitions translate product vision into concrete, testable units by specifying acceptance criteria for each feature. This Skill structures feature decomposition within planning documents to ensure requirements are clear and measurable for orchestrator task implementation.

What's the best way to map user flows in a planning document?

User flow mapping identifies key journeys and pain points by tracing interactions through the product. This Skill integrates user flows into planning documents alongside vision and features, producing a structured JSON artifact that aligns flows with technical and functional requirements.

Do I need prior planning experience to create planning documents for new orchestrator tasks?

No special experience is required. This Skill handles the structuring and formatting. You provide product vision, core features, user flows, and requirements; the Skill outputs a formal JSON planning artifact conforming to orchestrator project specifications.