lead

Coordinate multi-agent project execution across structured phases via GitHub Issues.

1|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/dokipen/claude-cadence --skill lead-dokipen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lead
Source: https://github.com/dokipen/claude-cadence/tree/main/.gemini/skills/lead
Command: npx skills add https://github.com/dokipen/claude-cadence --skill lead-dokipen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, gh, issues, docker, and includes scripts (resource) components.

What problem does it solve?

Coordinate multi-agent project execution across structured phases, tracked via a ticket provider (GitHub Issues or issues-api).

Core Features & Use Cases

  • End-to-end workflow coordination across Phase 0–7 with autonomous agent delegation
  • Ticket-driven project governance including worktree management and lifecycle transitions
  • Plan, human-activity, and verification workflows integrated with CLAUDE.md-driven project standards

Quick Start

Start by creating or selecting a worktree and initiating Phase 0 of the lead workflow.

Frequently Asked Questions about lead

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

FAQPage Schema
How do I coordinate multi-agent project execution across structured workflow phases?▼

Multi-agent project execution is coordinated by routing work through structured Phase 0–7 transitions, delegating tasks to specialist agents, and tracking progress via GitHub Issues or issues-api for auditable governance.

How does agent delegation work with worktree management for project planning?▼

Agent delegation works by assigning phase-specific tasks to sub-agents while managing isolated worktrees, ensuring that implementation, verification, and cleanup happen in controlled environments tracked by the ticket provider.

Do I need GitHub Issues and jq to use this workflow coordination approach?▼

Yes, workflow coordination requires jq, gh CLI, issues-api, and Docker to manage ticket-driven governance, execute lifecycle transitions, and enforce policy-driven phase progressions across the project.

Can I enforce custom verification and human activity workflows within autonomous agent coordination?▼

Custom verification and human activity workflows are enforced by applying specific labels that trigger Plan or Human Activity modes, overriding autonomous transitions to ensure policy-driven project standards are met.

What is the best way to track ticket-driven project governance across multiple agents?▼

Ticket-driven project governance is tracked by integrating lifecycle transitions directly through GitHub Issues or the issues-api, ensuring every phase completion and agent delegation is traceable and auditable.

When should I not use autonomous agent delegation for implementation work?▼

Autonomous agent delegation should not be used when projects lack structured CLAUDE.md-driven standards or when tasks require manual oversight outside the defined Phase 0–7 workflow boundaries.