sprint-conductor

Route ordered child issues sequentially through ADL lifecycle and editor skills.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill sprint-conductor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-conductor
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/sprint-conductor
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill sprint-conductor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinates a single sprint issue through an ordered list of child issues by routing them one-at-a-time via the existing ADL lifecycle and editor skills, ensuring deterministic progress, auditability, and bounded review/closeout.

Core Features & Use Cases

  • Sequential sprint orchestration: drives one concrete sprint issue and an explicit ordered issue list through the standard lifecycle, preventing parallel execution.
  • Guided lifecycle routing: leverages existing workflow/conductor and editor skills to avoid reimplementation and maintain traceable state.
  • State and evidence discipline: records sprint state, tracks PRs and artifacts, and assembles bounded sprint reviews and closeouts for auditability.
  • Guardrails and policy compliance: validates readiness, performs truth checks against GitHub state, and enforces closeout gates before advancing.

Quick Start

Provide the repository root and an ordered list of child issues, then run sprint-conductor to orchestrate and close out the sprint.

Frequently Asked Questions about sprint-conductor

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

FAQPage Schema
How do I automate sprint orchestration to prevent parallel execution of issues?

Sprint orchestration automates issue routing by driving an ordered list of child issues through the standard lifecycle sequentially. It operates as a slow-path supervisor, ensuring one issue is fully closed before the next to enforce deterministic progress and prevent parallel execution.

How does sprint closeout enforce policy compliance and auditability?

Sprint closeout enforces auditability by recording sprint state artifacts, tracking PRs, and assembling bounded reviews. It performs truth checks against GitHub state and enforces closeout gates before advancing, ensuring every issue satisfies deployment requirements and policy compliance.

Can I use sprint-conductor with my existing workflow and editor skills?

Yes, sprint orchestration leverages existing workflow and editor skills to route issues through the standard ADL lifecycle. This avoids reimplementation and maintains traceable state by relying on your established automation components and lifecycle infrastructure.

What do I need to provide to start automated sprint orchestration?

You need to provide the repository root and an explicit ordered list of child issues to start automated sprint orchestration. The supervisor then sequentially routes these issues through the existing lifecycle, tracking state artifacts and enforcing closeout gates.

When should I not use sequential sprint orchestration for issue tracking?

You should avoid sequential sprint orchestration when your workflow requires parallel execution or concurrent issue processing. This supervisor operates strictly as a slow-path orchestrator, enforcing that one issue is fully closed before advancing to the next child issue.