<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Heimdall</title><link>/</link><description>Recent content on Heimdall</description><generator>Hugo</generator><language>en-us</language><atom:link href="/index.xml" rel="self" type="application/rss+xml"/><item><title>About Heimdall</title><link>/docs/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/about/</guid><description>&lt;h2 id="overview">Overview &lt;a href="#overview" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Heimdall is a CLI for building &lt;strong>deterministic agentic workflows&lt;/strong> from YAML. User-defined workflows describe the phases, gates, feedback loops, artifacts, and completion criteria that guide agentic work. Agents provide the intelligence; Heimdall owns the structure.&lt;/p>
&lt;p>Each run executes in an &lt;strong>isolated git worktree&lt;/strong>, so teams can run fixes and implementation tasks in parallel without mixing changes.&lt;/p>
&lt;h2 id="the-problem">The problem &lt;a href="#the-problem" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>AI agents are powerful, but the process around them is often implicit:&lt;/p></description></item><item><title>Getting started</title><link>/docs/getting-started/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/getting-started/</guid><description>&lt;h2 id="prerequisites">Prerequisites &lt;a href="#prerequisites" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>When the CLI ships, you will need:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Node.js&lt;/strong> 22 or later&lt;/li>
&lt;li>&lt;strong>Git&lt;/strong> with worktree support&lt;/li>
&lt;li>A repository where agents will make changes&lt;/li>
&lt;/ul>
&lt;h2 id="install-preview">Install (preview) &lt;a href="#install-preview" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Installation instructions are not finalized. The intended experience will look like:&lt;/p>



 
 
 

 
 
 
 

 

 &lt;div class="prism-codeblock ">
 &lt;pre id="9f230e3" class="language-bash ">
 &lt;code>npm install -g heimdall
heimdall --version&lt;/code>
 &lt;/pre>
 &lt;/div>
&lt;h2 id="initialize-a-workflow">Initialize a workflow &lt;a href="#initialize-a-workflow" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>Create a &lt;code>workflows/&lt;/code> directory in your repository and add a workflow definition:&lt;/p>



 
 
 

 
 
 
 

 

 &lt;div class="prism-codeblock ">
 &lt;pre id="362a45a" class="language-yaml ">
 &lt;code># workflows/fix-issue/workflow.yaml
name: fix-issue
description: Triage, implement, validate, and open a PR for an issue.

phases:
 - id: plan
 agent: spec-planner
 gate: plan-approved

 - id: implement
 agent: ts-engineer
 artifacts:
 - src/**

 - id: validate
 command: npm run quality
 on_failure: implement

 - id: review
 agent: ts-code-reviewer
 on_failure: implement

 - id: publish
 command: heimdall pr create&lt;/code>
 &lt;/pre>
 &lt;/div>

&lt;div class="alert alert-info d-flex" role="alert">
 &lt;div class="flex-shrink-1 alert-icon">
 
 &lt;span class="material-icons size-20 me-2">
 info
 &lt;/span>&lt;/div>
 
 &lt;div class="w-100">This YAML is illustrative. The workflow schema will be documented when the engine stabilizes.&lt;/div>
 &lt;/div>
&lt;h2 id="run-a-workflow">Run a workflow &lt;a href="#run-a-workflow" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>


 
 
 

 
 
 
 

 

 &lt;div class="prism-codeblock ">
 &lt;pre id="d221739" class="language-bash ">
 &lt;code># Run against the current repo; Heimdall creates an isolated worktree
heimdall workflow run fix-issue --issue 42

# Inspect run status
heimdall workflow status --run-id wf_01HXYZ&lt;/code>
 &lt;/pre>
 &lt;/div>
&lt;p>Each run gets its own git worktree under &lt;code>.heimdall/worktrees/&lt;/code>, keeping parallel agent tasks isolated.&lt;/p></description></item><item><title>Workflow examples</title><link>/docs/guides/workflows/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/guides/workflows/</guid><description>&lt;p>The examples below are &lt;strong>invented previews&lt;/strong> of how Heimdall workflows might look. They are not wired to a live engine yet — they demonstrate structure, gates, and code blocks in the docs theme.&lt;/p>
&lt;h2 id="collect-user-input-to-file">Collect user input to file &lt;a href="#collect-user-input-to-file" class="anchor" aria-hidden="true">&lt;i class="material-icons align-middle">link&lt;/i>&lt;/a>&lt;/h2>&lt;p>A simple workflow that prompts for content and writes it to a file:&lt;/p>



 
 
 

 
 
 
 

 

 &lt;div class="prism-codeblock ">
 &lt;pre id="9ebf592" class="language-yaml ">
 &lt;code>name: collect-user-input
description: Prompt for text and save it to a file in the worktree.

phases:
 - id: prompt
 agent: input-collector
 prompt: |
 Ask the user what they want to save, then write the response
 to `output/user-notes.md` in the worktree.

 - id: verify
 gate: file-exists
 path: output/user-notes.md&lt;/code>
 &lt;/pre>
 &lt;/div>
&lt;p>Run it (preview):&lt;/p></description></item></channel></rss>