ddx

name

ddx

description

Operates the DDx toolkit for document-driven development. Covers beads (work items), the queue, executions, agents, harnesses, personas, reviews, spec-id. Use when the user says "do work", "drain the queue", "run the next bead", "execute a bead", "review this", "review with fresh eyes", "fold in this guidance", "review again", "break this down into specs and beads", "make this testable", "check against spec", "what's on the queue", "what's ready", "what's blocking the queue", "create a bead", "file this as work", "run an agent", "dispatch", "use a persona", "how am I doing", "ddx doctor", or mentions any ddx CLI command.

DDx

DDx (Document-Driven Development eXperience) is a CLI platform for document-driven development. It ships a bead tracker (portable work items with acceptance criteria), a task-execution boundary (DDx forwards raw passthrough constraints for harness, provider, model, and profile while power travels as MinPower/MaxPower bounds; Fizeau owns concrete routing, provider/model discovery, aliases, fuzzy matching, catalog lookups, and transcript/session rendering), a persona system (bindable AI personalities), a library registry (plugins with prompts, templates, personas), and git-aware synchronization. This skill makes any skills-compatible coding agent (Claude Code, OpenAI Codex, Gemini CLI, etc.) understand and operate the DDx surface correctly.

How this skill works

The skill body you're reading is an overview plus an intent router. The real domain guidance lives in reference/*.md files.

Directive: before responding to any DDx-related request, read the matching reference file from the router table below. The router is not optional — your answer must be grounded in the reference file's guidance, not this overview alone.

Vocabulary

Single source of truth for DDx terms. Every reference file uses these exact definitions.

• Bead — a portable work item (task, bug, epic, chore) with metadata, dependencies, and acceptance criteria. ddx bead create.
• Queue — the set of active beads. The execution-ready queue is status=open work whose dependencies are closed and which is not parked by cooldown, supersession, or execution-eligibility policy. ddx bead ready, ddx bead status.
• Lifecycle status — the persisted bead state: proposed, open, in_progress, blocked, closed, or cancelled.
• Ready — a bead whose dependencies are all closed and which is eligible to be picked up next. ddx bead ready.
• Blocked — status=blocked work paused by a hard external recheckable blocker. Ordinary dependency waits are derived queue state, not blocked status. ddx bead blocked.
• Proposed — work awaiting operator decision before autonomous execution. Proposed beads are not worker-eligible until accepted, rewritten, split, blocked externally, cancelled, or otherwise resolved.
• Claim — mark a bead as in-progress by an agent (concurrent-write protection). ddx bead update <id> --claim.
• Close — mark a bead as done, with evidence (session, commit SHA). ddx bead close <id>. Beads only close on execution outcomes success or already_satisfied.
• Run — one task invocation atom. ddx run calls Fizeau Execute once with prompt/config, MinPower/MaxPower bounds, and optional raw passthrough constraints.
• Try — one bead attempt in an isolated worktree. ddx try <id> wraps ddx run with bead prompt resolution, evidence capture, and merge/preserve finalization.
• Work — drain the bead queue. ddx work picks ready beads and invokes ddx try; it owns queue iteration and retry policy.
• Execution — a generic DDx execution run (FEAT-010). Includes execution definitions, execution records, and execution evidence under .ddx/runs/<id>/.
• Agent — an AI coding agent (Claude, Codex, Gemini, etc.) invoked via a harness. Not a subagent (harness-specific — see below).
• Harness — a Fizeau routing concept. DDx may pass --harness as an operator-supplied constraint, but DDx does not validate, rank, fallback, or branch on harness names.
• Persona — a Markdown file (YAML frontmatter + body) that defines an AI personality. DDx injects the body as a system-prompt addendum to ddx run. ddx persona list/show/bind.
• Role — an abstract function (e.g., code-reviewer, test-engineer) a workflow can reference. Projects bind roles to personas.
• Binding — a project-specific role: persona map in .ddx/config.yaml under persona_bindings.
• Power bounds — MinPower and optional MaxPower integers passed to the upstream execution service. DDx may raise MinPower on eligible retries; Fizeau owns concrete route selection within those bounds.
• Plugin — a self-contained extension installed to .ddx/plugins/<name>/. The default ddx plugin (personas, prompts, patterns, templates) is auto-installed by ddx init. ddx install <name>.
• Skill — an agentskills.io-standard directory (SKILL.md + optional reference/, evals/, scripts/). This ddx skill is the one DDx ships. Plugins can ship additional skills.
• Subagent — a harness-local concept for running a prompt in an isolated context (Claude Code's .claude/agents/ + context: fork; Codex's agents/; others differ). DDx does not specify subagent orchestration; that remains harness business.
• Update — refresh plugin/toolkit content to a newer version. ddx update [<plugin>].
• Upgrade — replace the DDx binary with a newer release. ddx upgrade.
• Review — two distinct concepts. Bead review (ddx bead review <id>) grades a completed bead against its acceptance criteria. Comparison/adversarial review is a workflow skill composition over ddx run, not a core quorum flag. See reference/review.md.
• Governing artifact — the document that authorizes a bead's work: a FEAT-*, SD-*, TD-*, or ADR-* under docs/. Referenced via spec-id.
• Spec-id — the spec-id: <ID> custom field on a bead pointing at its governing artifact.

Intent router

Before responding, read the matching file.

User says / asks about	Read this file
"what should I work on next", "what's blocking the queue", "review with fresh eyes", "fold in this guidance", "review again", "break this down into specs and beads", "make this testable", broad queue orientation or planning	reference/interactive.md
write/plan work, "create a bead", "file this as work", bead metadata, acceptance criteria, dependencies	reference/beads.md
ddx work, ddx try <id>, "execute bead <id>", "drain the queue", "run the next bead", "start the worker", "start N workers and watch", "monitor the drain", verify-and-close	reference/work.md
"review this", "check against spec", bead review, quorum review, code review, adversarial check	reference/review.md
"assess bead readiness", "score a bead", "triage a failed attempt", "refine a bead", bead authoring lint	bead-lifecycle/
"run an agent", "dispatch", harness/provider/model passthrough, power, effort, "use a persona", role bindings	reference/agents.md
"what's on the queue", "what's ready", "how am I doing", health check, "ddx doctor", sync status	reference/status.md

If the intent spans multiple files (e.g., "create a bead and then run it"), read beads.md first, then work.md. If no match, ask the user which concept they mean rather than guessing.

Top-level policy reminders

These apply across all DDx operations. Do not restate them in every reference file; do not violate them.

• Never edit .ddx/beads.jsonl directly. All tracker changes go through ddx bead create/update/close/dep. Direct edits corrupt bead history and cannot be audited.
• Tracker changes are commit-worthy. After ddx bead create, update, dep add/remove, or close, commit the resulting .ddx/beads.jsonl change — either as a tracker-only commit or folded into the same commit as related implementation changes.
• Preserve bead-attempt commit history. Branches containing ddx try / ddx work execution commits carry an audit trail. Never squash, rebase, filter, or amend these commits. Use only git merge --ff-only or git merge --no-ff when merging. gh pr merge --squash and --rebase are forbidden on these branches.
• Work in worktrees for parallel agents. Use wt switch -c <branch> (worktrunk) or equivalent to give each concurrent agent its own isolated checkout. ddx try does this automatically; manual parallel work should too.
• Power-first execution dispatch. Default to ddx run/ddx try/ddx work with power bounds. --harness, --provider, and --model are passthrough constraints only; DDx must not use them for routing policy.

Links out

• Full CLI reference: ddx --help, ddx <subcommand> --help.
• Governing feature specs: see FEAT-* documents under your project's docs/ tree — especially the CLI, beads, agent-service, executions, and skills features.
• Personas README: shipped by the default ddx plugin at .ddx/plugins/ddx/personas/README.md.
• Open standard this skill conforms to: agentskills.io.