coordinating

Coordinate delegated development workflows from issue intake through PR readiness.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/arthur-debert/dodot --skill coordinating
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinating
Source: https://github.com/arthur-debert/dodot/tree/main/.agents/skills/coordinating
Command: npx skills add https://github.com/arthur-debert/dodot --skill coordinating

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps a top-level agent coordinate delegated development work without mixing orchestration and implementation, so issue work, epics, and PR lifecycles stay organized and controlled.

Core Features & Use Cases

  • Workstream orchestration: Gather context, brief implementers, and spawn isolated Trees for standalone issues or epic workstreams.
  • PR lifecycle driving: Use the shipit PR engine to monitor status, wait for reviews, address feedback through shepherds, and flip PRs to ready at the correct point.
  • Epic management: Integrate workstreams into epic branches, run convergence for fallout, and prepare the umbrella PR for human merge.
  • Durable learning capture: Move lasting process knowledge into repo files such as ADRs, docs, and CONTEXT.md updates instead of leaving it in session memory.

Quick Start

Use the coordinating skill to assess the current issue or epic, gather the needed repo context, and then spawn the appropriate implementer with a complete brief.

Frequently Asked Questions about coordinating

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

FAQPage Schema
How do I coordinate delegated development work across multiple pull requests?

Coordinate delegated development by gathering context and briefing implementers to spawn isolated Trees, keeping orchestration separate from implementation to organize issue work, epics, and PR lifecycles.

What is the best way to manage epic workstreams and PR readiness?

Manage epic workstreams by integrating them into epic branches, running convergence for fallout, and using the shipit PR engine to monitor status and flip PRs to ready for human merge.

How do I orchestrate PR review loops without mixing in implementation logic?

Orchestrate PR review loops by using the shipit PR engine to wait for reviews and address feedback through shepherds, ensuring the coordinating agent strictly handles lifecycle management rather than code changes.

Do I need shipit logs to orchestrate workstream lifecycles?

Yes, authoritative workstream orchestration requires shipit logs along with shipit spawn, shipit pr status, shipit pr next, shipit pr wait, and shipit pr ready to drive delegated development workflows.

How do I capture durable process knowledge from an orchestrated code review?

Capture durable process knowledge by moving lasting insights from session memory into repository files such as ADRs, docs, and CONTEXT.md updates instead of leaving them in temporary orchestration memory.

Can I use this orchestration approach for standalone issues outside of epics?

Yes, workstream orchestration applies to standalone issues by allowing the top-level agent to assess the issue, gather repo context, and spawn an isolated implementer Tree with a complete brief.