Pipeline

Helm organizes work into 5 phases with 13 agents (11 pipeline, 1 on-demand, 1 orchestrator). Each agent has a clear mission, defined inputs and outputs, and quality thresholds that must be met before progressing.

Phases

PhasePurposeAgents
DiscoverUnderstand the problemScout/Survey, Research
PlanDefine the solutionPlanning, Architect, Roadmap, Breakdown
QualityValidate the planReview (95% gate)
BuildImplement codeBuild
DeployTest and shipVerify (95% gate), Ship

Greenfield Flow

For new projects starting from scratch:

scout → research → planning → architect → roadmap → breakdown → review → build → verify → ship

Scout explores requirements through conversation — what are you building, for whom, and why?

Brownfield Flow

For existing codebases:

survey → research → planning → architect → roadmap → breakdown → review → build → verify → ship

Survey scans the codebase first — tech stack, architecture, integrations, technical debt — then Research extracts what needs to change.

How Agents Hand Off

Every agent produces a handoff document stored at .helm/handoffs/{agent}.md. Handoffs have two layers:

The next agent reads the handoff before starting work. If the handoff is missing or incomplete, the orchestrator blocks progression.

Quality Gates

Two critical checkpoints ensure quality:

GateAgentThresholdWhat It Validates
Plan GateReview95%Traceability: Research → PRD → Phases → Tasks → Acceptance Criteria
Build GateVerify95%Tests pass, SAST clean, code follows architecture, acceptance criteria met

Verdicts

Status Dashboard

Run helm status to see pipeline progress:

  Helm v0.1.0

  Project:  my-api
  Type:     brownfield
  Phase:    build
  Profile:  guided

  Pipeline:
    [done]  survey       100%
    [done]  research     100%
    [done]  planning     100%
    [done]  architect    100%
    [done]  roadmap      100%
    [done]  breakdown    100%
    [done]  review       100%
    [>>  ]  build        in progress
    [    ]  verify       pending
    [    ]  ship         pending