cdd-workflow

Analyze plan.md to detect project state and route work to the matching Agent Skill.

Updated Mar 12, 2019
One-click install
npx skills add https://github.com/gustavofsantos/dot-files --skill cdd-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdd-workflow
Source: https://github.com/gustavofsantos/dot-files/tree/main/.agents/skills/cdd
Command: npx skills add https://github.com/gustavofsantos/dot-files --skill cdd-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Context-Driven Development Orchestrator analyzes plan.md to detect the Project State and delegates to the appropriate Agent Skill (Persona), ensuring the correct workflow phase is executed with aligned roles.

Core Features & Use Cases

  • State detection: reads plan.md to determine the required role (Analyst, Architect, Executor, Integrator).
  • Dynamic role adoption: switches to the corresponding Agent Skill and executes its protocol.
  • Guardrails and guidance: enforces the cdd recite protocol to maintain alignment in long-running sessions.

Quick Start

Analyze plan.md and activate the matching Agent Skill based on the project state.

Frequently Asked Questions about cdd-workflow

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

FAQPage Schema
How do I automate agent skill routing based on project state?

Automate agent skill routing by analyzing a plan.md file to detect the current project state and dynamically delegating execution to the matching persona, such as Analyst, Architect, or Executor.

What is context-driven development orchestration for plan-driven workflows?

Context-driven development orchestration reads plan.md to determine the required workflow phase and switches to the corresponding agent skill, ensuring the correct role protocol is executed with aligned tasks.

How do I maintain role alignment in long-running agent workflows?

Maintain role alignment in long-running agent workflows by enforcing a recite protocol with guardrails that keep the active persona consistent throughout the session based on the detected plan state.

Do I need a plan.md file to trigger agent personas like Architect or Executor?

Yes, a plan.md file is required to detect the project state and route work to the appropriate agent skill, as the orchestrator relies on it to determine and activate the matching persona protocol.

Can I use workflow routing for software engineering without predefined agent skills?

No, workflow routing requires a resolved set of agent skills to execute the corresponding protocol once the project state is detected from plan.md, ensuring the correct persona is adopted.

What is the best way to switch between Analyst and Integrator roles during a project?

Switch between Analyst and Integrator roles by using a context-driven orchestrator that reads plan.md to detect phase changes and dynamically adopts the appropriate agent skill for execution.