cdt

Coordinate multi-agent development workflows across plan, dev, full, and auto modes.

10|2|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/rube-de/cc-skills --skill cdt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdt
Source: https://github.com/rube-de/cc-skills/tree/main/plugins/cdt/skills/cdt
Command: npx skills add https://github.com/rube-de/cc-skills --skill cdt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinates multi-agent development workflows using specialized agent teammates to plan, implement, test, and review software changes with governance and handoff artifacts.

Core Features & Use Cases

  • Four modes: plan, dev, full, and auto, enabling staged collaboration.
  • Defined teammate roles: Architect, Product Manager, Developer, Code-Tester, QA-Tester, and Reviewer, plus a Researcher subagent.
  • Produces plans and artifacts (plan.md, ADRs) and orchestrates cross-team messaging and reviews.
  • Ideal for complex tasks that benefit from parallel experimentation, governance gates, and structured handoffs.

Quick Start

Provide your task and choose a mode to generate the plan and start the multi-agent team.

Frequently Asked Questions about cdt

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

FAQPage Schema
How do I orchestrate multi-agent development workflows for complex software changes?

Multi-agent development workflows are orchestrated by coordinating specialized agent teammates across plan, dev, full, and auto modes to execute end-to-end software changes. It assigns defined roles like Architect, Developer, and Reviewer to handle dependency-driven tasks and governance gates.

What's the best way to manage agent teams for software architecture planning and ADR generation?

Managing agent teams for architecture planning is handled through the plan mode, which coordinates an Architect agent to produce plan artifacts and Architecture Decision Records (ADRs). This ensures structured governance and clear handoff material before development begins.

Can I use automated testing and review gates within an agent-team development workflow?

Automated testing and review gates are enforced within the full and auto modes by assigning Code-Tester, QA-Tester, and Reviewer agents. This ensures dependency-driven task execution validates code quality and governance before final handoff.

When do I need a multi-agent team with defined roles for a software development workflow?

A multi-agent team with defined roles is needed for complex software tasks that benefit from parallel experimentation, structured governance, and cross-team messaging. It ensures end-to-end changes are properly planned, tested, and reviewed by specialized agents.

Does multi-agent orchestration work without external dependencies to coordinate development tasks?

Multi-agent orchestration works without external dependencies, relying entirely on internal references to coordinate the agent teams. It generates its own governance prompts, plan artifacts, and cross-team messaging to drive the development workflow.

What is the difference between plan, dev, full, and auto modes in agent-team orchestration?

The modes represent staged collaboration phases: plan generates architecture and ADR artifacts, dev executes implementation, full applies testing and review gates, and auto enables end-to-end orchestration across all defined agent roles.