dcp-lead-init

Start Deep Co-Planning lead role for a task with human oversight.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Koryto/dotagent --skill dcp-lead-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dcp-lead-init
Source: https://github.com/Koryto/dotagent/tree/main/.agent/playbooks/deep-co-planning/skills/dcp-lead-init
Command: npx skills add https://github.com/Koryto/dotagent --skill dcp-lead-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start Deep Co-Planning as the lead for an active planning run, binding the lead role to a specific task to kick off and govern the planning session with human oversight.

Core Features & Use Cases

  • Initialize the planning workspace with human guidance and co-author the high-level design with the human.
  • Maintain the live round packet, ingest reviewer outputs, classify feedback, and produce reviewer-facing carry-forward results.
  • Derive one or more specs from the approved high-level design, track known unknowns, and manage round progress according to the defined rules.

Quick Start

Start the lead run by specifying the task name via the Deep Co-Planning playbook.

Frequently Asked Questions about dcp-lead-init

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

FAQPage Schema
How do I initialize a lead role for multi-round planning sessions?

You initialize a lead planning role by starting the Deep Co-Planning run via explicit CLI invocation, binding the lead to a specific task to govern multi-round planning with human input and reviewer feedback.

What is Deep Co-Planning and how does its lead role work?

Deep Co-Planning is a session format requiring centralized leadership where the lead co-authors high-level designs with humans, manages live round packets, and classifies reviewer feedback to produce carry-forward results.

How do I manage reviewer feedback during planning rounds?

You manage reviewer feedback by ingesting reviewer outputs into the live round packet, classifying the feedback, and producing reviewer-facing carry-forward results to track round progress according to defined rules.

Do I need explicit task scoping to start a co-planning session?

Yes, explicit task scoping is required. The lead role must be bound to a specific task to satisfy operational requirements for human-in-the-loop governance and live round management during the planning run.

Can I derive specs directly from an approved high-level design?

Yes, you can derive one or more specs from the approved high-level design. The lead tracks known unknowns and manages round progress to transition from the design phase into actionable specifications.

What are the limitations of centralized leadership in planning rounds?

Centralized leadership in planning rounds requires continuous human-in-the-loop governance and explicit CLI invocation, meaning the process cannot operate autonomously and depends on active human oversight for round creation.