cdd-dev

Kairos CDD-Dev

Executes planned tasks through the engine's implement / review / fix chain — its own orchestrator decisions (mode chain, final review) following the engine's next: line, with no installed-engine precondition (npx pulls the engine on demand); on closure the engine's next: face carries the pipeline continuation.

Invocation discipline — every engine command runs via npx -y @oscaner-skills/cdd-engine@latest <subcommand> as a background dispatch: launch it in the background and await the completion notification — never poll — then read the full output (stdout/stderr). Output filtering is forbidden — no piping to tail/head, no 2>&1 |, no EXIT=$? capture. Round rhythm — one review pass per dispatch; a fix round re-enters the review while the route is not done; the implement child commits its own work; ensure the working tree is clean before entering review (dirty → BLOCKED); the orchestrator writes no tree during dispatch. Failure face — cross-node failure handling lives in the Failure Modes table below (the single source); node Fail entries keep only local behavior.

Flow Digraph

flowchart TD
  A[determine-base] --> B[set-base]
  B --> C[implement-wave]
  C --> L[NEXT-LOOP]
  L -->|until next is terminal| L
  L -->|no next| Z1((BLOCKED))

Node Definitions

determine-base

• Do: Resolve the base branch — inference sources in order: plan base field → branch upstream (git rev-parse --abbrev-ref @{u}) → conversation context; if none yields a definitive base, ask the user — do not guess. The base may already be present in the artifact (npx -y @oscaner-skills/cdd-engine@latest base get --plan <path>); skip inference when the artifact is present.
• Read: plan document + git upstream + conversation context + npx -y @oscaner-skills/cdd-engine@latest base get --plan <path>
• Exit: base resolved → set-base
• Fail: user refuses to confirm → BLOCKED: base-undecided

set-base

• Do: Persist the base via the engine CLI — npx -y @oscaner-skills/cdd-engine@latest base set --plan <path> --base <branch> --source <enum>, where source is plan-field | branch-upstream | conversation-context | user-confirmed. The engine is the sole write/read path for the artifact — never hand-write it; set is idempotent, refusals and validation errors are engine-handled.
• Read: npx -y @oscaner-skills/cdd-engine@latest base get --plan <path> (the artifact on stdout)
• Exit: artifact written (or already present) → implement-wave
• Fail: engine refusal / validation error → report to user; user decides (no hand-written artifact)