planner-orchestration

Enforces single-session, user-controlled model checkpoints for planned implementation workflows.

733|110|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/kdlbs/kandev --skill planner-orchestration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner-orchestration
Source: https://github.com/kdlbs/kandev/tree/main/.agents/skills/planner-orchestration
Command: npx skills add https://github.com/kdlbs/kandev --skill planner-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-phase AI development work often loses control over which model runs which phase, when delegation is authorized, and how durable artifacts like plans and work orders are handed off. This Skill enforces a single-session orchestration model where the user explicitly controls model selection, implementation authorization, and subagent delegation.

Core Features & Use Cases

  • Model Checkpoints: Separates design (strong model), execution, and escalation phases so the user picks the model at each stage instead of the harness.
  • Work-Order Workflow: Structures feature work into requirements, system designs, plans, and status-tracked work orders stored under docs/specs and docs/plans.
  • User-Authorized Subagents: Permits parallel delegation only after explicit user approval, using the platform's native delegation tool with disjoint file ownership.
  • Use Case: A developer designs a feature with a strong model, hands off a design package, switches models, then explicitly requests implementation; the agent executes work orders sequentially with TDD and records verification results.

Quick Start

Apply the planner-orchestration workflow to plan and implement this feature using spec-driven work orders with user-controlled model checkpoints.

Frequently Asked Questions about planner-orchestration

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

FAQPage Schema
How do I control which AI model runs each development phase?

Use model checkpoints that keep each phase in the primary conversation so the user selects the model. Design uses a strong model, execution begins only after an explicit implementation request, and escalation back to a stronger model happens before architectural or security decisions.

How to structure work orders for spec-driven development?

Store requirements in docs/specs/<system>/requirements/, designs in system-design/, and plan.md with sibling work orders in docs/plans/<initiative>/. Each work order includes requirement IDs, scope, owned files, acceptance criteria, exact verification commands, and a pending/in_progress/done status.

When can I use subagents for parallel task execution?

Subagents require explicit user authorization after the implementation model is selected. Only tasks marked parallel-safe with disjoint files and no shared schema, migration, or lockfile may be delegated, using the platform's native delegation tool with fork_turns set to none.

Should I run code review or QA before opening a PR?

No, the work order's TDD requirement and recorded verification results are the pre-PR evidence. Run /simplify, /qa, /code-review, or broad /verify only when the user explicitly asks or an actionable PR/CI finding requires focused remediation.

What are the limitations of plan wave labels for parallelization?

Plan waves and parallel-safe labels are planning information only and never authorize launching implementation workers. The user must explicitly request subagents, and worktrees must not be created solely to parallelize plan tasks without that authorization.