What does the auto pipeline automate?
It is designed to move through the Hal workflow phases such as planning, conversion, validation, implementation, reporting, and archive behavior. Check the current source docs for exact command behavior.
Feature 06
Move through planning, conversion, validation, implementation, reporting, and archive behavior as one explicit coding loop.
Why it matters
Hal turns agent work into a named sequence. Instead of one open-ended chat, the loop moves through explicit phases that are easier to inspect and repeat.
Hal’s auto pipeline is the explicit sequence around PRD-driven AI coding work: plan the requirement, convert it into workflow state, validate stories, run implementation, preserve reports, and review the result. The pipeline makes checkpoints visible instead of burying them inside one open-ended agent chat.
Chat is flexible, but it is a weak production workflow. The boundaries are soft, the sequence is easy to skip, and the review trail can disappear inside the conversation.
Hal makes the loop explicit.
A Hal run moves through named phases: plan the work, convert requirements, validate stories, run implementation, and preserve reviewable state.
hal plan "describe the product change"
hal convert
hal validate
hal runEach step has a job. Each step gives the developer a place to inspect the work.
Start with a small feature. Confirm the plan is specific, validation passes, the agent changes only relevant files, and the resulting state is understandable before expanding to larger work.
| Hal does | Hal does not do |
|---|---|
| Structures PRD-native coding loops around planning, validation, implementation, reporting, and reviewable state. | Guarantee code quality, passing tests, delivery speed, revenue, rankings, or production readiness. |
| Helps supported engines work against smaller, reviewable units of work. | Replace developer review, QA, security review, or merge judgment. |
Before adopting this workflow, verify the current Hal source repository, install docs, pricing status, and machine-readable pricing. Check release notes and engine support before relying on Hal in production work.
Short answers before you put this into an agent workflow.
It is designed to move through the Hal workflow phases such as planning, conversion, validation, implementation, reporting, and archive behavior. Check the current source docs for exact command behavior.
Hal can run autonomous implementation loops, but developers should still review the resulting state before merging.
Named steps make the work easier to repeat, debug, and audit than a long chat session with unclear boundaries.
Keep exploring the pieces of a reviewable coding loop.
Turn product intent into stories, acceptance criteria, and reviewable state before an AI coding agent touches the repo.
Preserve progress, reports, workflow files, and loop state so AI coding work can be paused, inspected, and resumed.
Give each AI coding iteration the repo-specific commands, conventions, and review rules it needs to stay consistent.