Demos
Demos
Eight scenarios show HELIX in motion against the four-step core workflow Contract from the PRD: write the brief, check alignment, create the work plan, hand it to the runtime.
Every demo is a session record: a committed session.jsonl
(source) under docs/demos/<slug>/. The asciinema casts on
this page are deterministic re-renders produced at build time by
scripts/demos/render_session.py. Capture the session once, verify it,
rebuild the cast whenever you like.
Install HELIX in your runtime
Three short reels show runtime install sessions. The committed recordings are historical session records; the text below names the current install path when a recording uses an older fallback.
In Claude Code, add the marketplace and install the plugin, then verify
with claude plugin list.
In Codex, the plugin manager installs HELIX from the configured marketplace. This recording still shows the Skills CLI fallback.
On Databricks Genie, fetch the single-file installer on a dev box and run it against your workspace.
adopt: Drop HELIX into an existing project
One install, one ask. The skill lands; the agent gains the artifact catalog and can scan whatever’s already in the repo. No CLI to learn.
brief: Author the governing artifacts
Vision → PRD → concerns → first feature spec, all populated from HELIX templates by the same skill the agent invokes. The brief is what the agent will defend code against on day n.
align: Detect drift across the artifact graph
PRD says one thing; a recent ADR says another. The helix skill walks the
graph from highest authority down and reports an ordered plan to close the gap.
plan: Identify planning gaps
The planning side of the same skill produces authority-ranked gaps. Each gap names the destination artifact, deliverable shape, next workflow mode, and evidence references. This demo stops before runtime work exists.
evolve: Thread a new requirement through the stack
The product-vision scenario, made concrete: a team adds OAuth alongside existing API-key auth. One sentence in; six authority-ranked steps out, spanning security architecture, ADRs, feature specs, designs, tests, and runtime work.
concerns: Catch technology drift before it ships
A project declares typescript-bun as its stack concern. The agent
writes idiomatic-looking code that nonetheless drifts to Node defaults.
Alignment catches all three drift signals.
review: Fresh-eyes audit against the same artifacts
A second agent inspects completed work against the artifacts that govern it. Two blocking findings (missing revocation enforcement, missing test), one warning (token leak in error log), filed as runtime work.
execute: Hand a bead to DDx
The runtime handoff. DDx selects the bead, routes to the configured harness, work runs in a worktree, acceptance gates fire, review runs, evidence appends, and the bead closes. HELIX stays offstage; its job was the artifacts.
Rebuilding the casts locally
python3 scripts/demos/render_session.py docs/demos/helix-align/session.jsonl
bash tests/validate-demos.shvalidate-demos.sh asserts schema soundness for every committed
session.jsonl and re-renders each into a byte-identical .cast. If
your render differs, either the record changed (rebuild + commit) or
the renderer changed (test will fail on every demo).