Skip to content
HelmIt

Workflow map

This map shows how a project moves through HelmIt. Preparation establishes a shared foundation; then each phase defines, implements, and verifies a delivery. You do not need to memorize the commands: /helmit:next reads the project’s position and shows the next step.

Workflow map Prepare once, deliver in phases

The first four steps prepare the project. The last three repeat for each delivery.

  1. Project preparation /helmit:setup Set up the project Create the HelmIt files and protect commits.
  2. /helmit:spec Define the product Record the goal, users, and requirements that guide deliveries.
  3. /helmit:arch Define the architecture Record technical choices and test, build, and lint commands.
  4. /helmit:env Check the environment Verify that the required tools are ready.
Each phase cycle
  1. /helmit:spec Define the delivery Describe the phase outcome and how to check that it is done.
  2. /helmit:implement Make the changes Organize tasks, implement changes, and verify each result.
  3. /helmit:ship Complete the phase Check the delivery and record its completion.

Next phase: return to the delivery spec.

May need your decision Checks a condition

How to read the map

Section titled “How to read the map”

Preparation belongs to the project, not to each conversation. The product spec guides every phase and can be revised if the direction changes. After the first /helmit:ship, the cycle starts again with the next phase’s spec. Each phase has its own tasks and proof. The delivery lifecycle explains that work in detail.

The colors highlight decisions and checks; they do not require human approval at every step. The agent uses decisions already made and asks you only when an unresolved choice could change the outcome. /helmit:chart lets you inspect the plan before implementation; /helmit:validate lets you check readiness before closing. Both are optional.

When the path changes

Section titled “When the path changes”

To resume after a pause, switch sessions, or find out what to do now, use /helmit:next. A localized correction can follow the CHG route outside the phases. If a phase is in progress, work returns to it after the CHG. See Inbox and corrections for that path.

If you are starting out, go to Install and get started. If you know the outcome you want but not the command, see Which command should I use?.