Using HELIX with DDx
DDx is the reference runtime integration for HELIX. Use it when you want HELIX’s artifact discipline connected to a dependency-aware tracker, an agent harness, and recorded execution evidence.
DDx is not required to use HELIX. It is one runtime that knows how to execute HELIX-shaped work.
Install the Reference Runtime
Install DDx, then install the HELIX package into DDx:
curl -fsSL https://raw.githubusercontent.com/DocumentDrivenDX/ddx/main/install.sh | bash
ddx install helixYou will also need an agent CLI supported by your local DDx setup, such as Claude Code or Codex.
Shape Work
Start by asking the runtime to frame your intent into governed artifacts and work items:
helix input "Build a REST API for managing bookmarks"That command is a DDx/HELIX integration surface. It turns sparse intent into Markdown artifacts plus tracked work that DDx can claim and execute.
You can also create DDx work items directly:
ddx bead create "Add OAuth login flow" --type task \
--labels helix,activity:build --set spec-id=FEAT-001 \
--acceptance "OAuth login redirects to provider and returns a session token"Execute with DDx
Once the artifacts and work items are ready, use DDx to drain the queue:
ddx agent execute-loopDDx claims ready work, dispatches the configured agent harness, records execution evidence, and closes completed items.
For one bounded pass:
ddx agent execute-loop --onceTransitional HELIX CLI Wrappers
Some HELIX CLI commands remain available for compatibility while DDx takes over runtime responsibilities:
helix run --agent claude --summary # Compatibility wrapper over DDx queue drain
helix build # Compatibility bounded build wrapper
helix start # Daemon mode with PID file
helix status # Check progress
helix stop # Stop the daemonPrefer DDx-owned commands for new automation. Treat the helix wrappers as
transitional integration shims, not the core HELIX product.
Interactive Agent Use
In an agent session with HELIX skills installed, you can steer DDx-backed work with natural language:
Use HELIX to frame OAuth support, create the governed work items, and then run
one bounded DDx execution pass.Or invoke integration commands directly if your agent exposes them:
| Command | What it does in the DDx integration |
|---|---|
/helix-input "build a bookmarks API" | Shape intent into governed artifacts and DDx work items |
/helix-align | Run a top-down alignment review over the artifact stack |
/helix-review | Fresh-eyes review of recent work |
/helix-run | Transitional wrapper over DDx queue drain |
/helix-build | Transitional wrapper for one bounded implementation pass |
/helix-triage "Fix login bug" | Create a DDx-tracked work item |
Related Reading
- Start with the runtime-neutral Getting Started guide.
- Browse the artifact-type catalog for HELIX templates.
- Review the projected HELIX self-artifacts for a worked example.