dev-orchestrator

Automate development ticket-to-PR workflows by coordinating subagents across phases.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/jcchikikomori/opencode-workflow --skill dev-orchestrator-jcchikikomori
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-orchestrator
Source: https://github.com/jcchikikomori/opencode-workflow/tree/main/skills/dev-orchestrator
Command: npx skills add https://github.com/jcchikikomori/opencode-workflow --skill dev-orchestrator-jcchikikomori

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates end-to-end development ticket-to-PR workflows by coordinating specialized subagents through a phased process with mandatory user gates.

Core Features & Use Cases

  • End-to-end orchestration across Requirements → Design → Sprint Plan → Implementation → Code Review → Pull Request, with user approval gates.
  • Modular agent-driven execution: loads subagents, passes deliverables between them, and tracks progress through defined phases.
  • Provides traceability and repeatable workflows for software projects, reducing cycle time and ensuring consistent outcomes.

Quick Start

Load the dev-orchestrator skill in an opencode session and provide a development ticket description to initiate the automated workflow.

Frequently Asked Questions about dev-orchestrator

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

FAQPage Schema
How do I automate the ticket-to-PR workflow for new software development tickets?

Ticket-to-PR workflow automation coordinates specialized subagents across requirements, design, sprint planning, implementation, code review, and pull request creation phases with mandatory user approval gates to ensure consistent development outcomes.

What is phased orchestration in software engineering automation?

Phased orchestration in software engineering automates end-to-end development workflows by loading specialized subagents, passing deliverables between them, and tracking progress through defined phases with gating user approvals at the sprint planning stage.

How do I execute per-task development cycles with code review and UI QA?

Per-task execution cycles run implementation tasks sequentially, followed by automated code review and UI QA checks with context-keeper logging, error handling, and progression rules to ensure quality before advancing to the next phase.

Can I gate user approvals during sprint planning in an automated development workflow?

User approval gating during sprint planning pauses the automated orchestration workflow before implementation begins, allowing stakeholders to review the design and sprint plan before subagents proceed with per-task execution and pull request creation.

What's the best way to coordinate specialized subagents for software project development?

Coordinating specialized subagents for software projects uses a modular agent-driven approach that loads subagents, passes deliverables between phases, and provides traceability with repeatable workflows to reduce cycle time and ensure consistent outcomes.