A brief that stays intact.
Helmweave saves the complete PRD snapshot and passes it to the scoped missions. Clarifications keep that snapshot even if the original file changes.
From a big idea
to a clear next move.
Give your agents more than a prompt. Give them a shared brief, a place to work, and a way to establish what’s done.
01 / START WITH THE WHOLE PICTURE Your brief.
Your brief.
An actionable beginning.
Choose a Markdown or plain-text PRD from the host. Ask for a prepared worktree and one mission per milestone. Keep the full brief connected to every scoped assignment.
product-brief.mdILLUSTRATIVE MISSION SEQUENCE
ONE SHARED WORKTREE
01 / FoundationPlan ready
PREREQUISITE
02 / Core experiencePlan ready
PREREQUISITE
03 / Release preparationPlan ready
One PRD. A connected set of missions.
A Markdown or plain-text PRD becomes scoped milestone missions. Request a new worktree explicitly and Helmweave prepares the shared checkout before workers start.
Planning can happen independently.
A checkout ready for the work.
Explicitly request a branch and worktree from a committed ref. Kickoff prepares and registers the shared workspace before workers start.
Progression you can see.
Arrange prerequisites in a dependency stack. Opt into automatic plan preparation, then review each next implementation plan before development.
Linked missions keep their own evidence. Planning-only completion or manual closure does not unlock the next implementation. Links across checkouts do not automatically merge code.
02 / MAKE DONE MEAN SOMETHING Work has a history.
Work has a history.
Outcomes have evidence.
Software and computer workflows distinguish what an agent changed, what the host checked, and what a reviewer observed.
- 01SCOPE + ACCEPTANCE
Plan the outcome
Inspect the project, define coherent tasks and dependencies, and agree on observable acceptance criteria. Choose the working checkout before implementation.
- 02IMPLEMENTATION
Develop with focus
Route bounded assignments to your chosen workers. Keep specialist roles, project context, and current instructions together as agents hand work off.
- 03TASK CHECKS
Test the changed behavior
Run focused checks for each task. Failed tests return to scoped repair before an independent verifier inspects the result.
- 04FRESH PERSPECTIVE
Assess independently
A read-only verifier examines the implementation, assertions, and current evidence. Its observations are recorded as agent evidence.
- 05INTEGRATION + REVIEW
Verify the combined goal
After tasks pass, check the composed outcome and run final review. When human observations are configured, they come after automated goal checks.
- 06DELIVERY
Finish deliberately
Complete under the configured policy. Git-backed human acceptance can save a local mission checkpoint; commit, merge, and deploy commands require explicit configuration and authorization.
Evidence follows the current work.
Steering that changes the expected behavior can invalidate affected evidence. Unchanged, valid checks can be retained during recovery; new or stale findings need fresh assessment. Verification supports an informed decision—it does not guarantee a bug-free result.
03 / A FLOW FOR THE WORK AT HAND Make the approach
Make the approach
your own.
Configure reusable templates with a starter prompt, workflow instructions, and a preferred runtime and agent. New missions receive a snapshot of that guidance.
PLANNING
Plan a goal
Explore constraints, open decisions, and a practical path forward. Findings only; no implementation pipeline.
RESEARCH
Research a decision
Compare options, evidence, tradeoffs, and uncertainty. Keep research separate from verified implementation.
VERIFIED SOFTWARE
Ship a code change
Plan, develop, run focused task checks, assess independently, and verify the combined outcome.
VERIFIED COMPUTER WORK
Verify a computer task
Define bounded browser or desktop actions and collect evidence of the resulting state through your agent’s tools.
Templates guide the work; current user instructions, execution scope, and host approval rules still apply. Choose agents and stage roles to fit your setup. Desktop automation depends on the selected agent and platform.
04 / KEEP THE THREADChange direction.
Change direction.
Keep your bearings.
The useful parts of a mission don’t disappear when the plan changes. Follow the live output, add guidance, inspect the history, and decide where the work goes next.
Steer without starting over.
Send task instructions or save shared decisions. Guidance is reconciled at safe boundaries, with applicable earlier requirements retained.
Checkpoint. Inspect. Branch.
Save selected eligible files to a local Git checkpoint. Inspect checkpoint history or branch a new mission to explore another direction.
Recover with context.
Inspect receipts and agent output, resolve a blocker, and retry with saved tasks. Targeted repairs can preserve completed work and valid evidence.
Hold the work when you need to.
Pause subsequent assignments, resume when ready, or archive and restore a mission. Manual completion is explicitly labelled “Completed by you.”
Build it with agents.
Run it like a normal project.
Helmweave’s delivery contract keeps useful source, fixtures, and setup instructions in the project. A focused portability scan looks for introduced harness dependencies and machine-specific paths before final software review.
Your normal install, development, build, and test commands remain the way in. Genuine application dependencies and services still need their documented setup.
Build your first mission