# Durable Workflows
{{< tier level="sovereign" note="Valdr Workflows make agent delivery repeatable, inspectable, and recoverable while keeping human authority explicit." >}}

Fast agents are not the same as reliable delivery. When work is scattered across prompts, terminals, and disconnected sessions, teams lose the context they need to explain an outcome, recover from a failure, or improve the next run.

**Valdr turns scattered agent activity into one governed run.** A workflow connects agents, tools, reviews, approvals, and results—so the process stays flexible without becoming a black box.

{{< youtube "afKZz_-qd7c" >}}

## Make every run better than the last

Valdr turns AI-assisted work into a system you can operate and improve:

- **Shape the work:** Make steps, inputs, results, dependencies, and human decisions explicit in the visual builder or a portable workflow definition.
- **Run with intent:** Coordinate agents and tools through one versioned process that can wait, resume, branch, and compose reusable child workflows.
- **See the evidence:** Follow step status, attempts, linked sessions, reviews, outputs, tool activity, and operator decisions from one run.
- **Improve the next run:** Use retained history as a baseline, make a focused change to routing, context, sequence, or gates, and run the process again.

Instead of asking whether an agent merely finished, you can understand **what ran, where work stopped, what supported each decision, and what to improve next**.

## Build the process around the work

Workflows give teams a durable foundation without forcing every team into the same process.

Smaller workflows can become purposeful building blocks inside a larger run. Parent and child runs remain separately inspectable, while their inputs, results, evidence, and recovery paths stay connected. You can grow a process without turning it back into an opaque chain of handoffs.

## One workflow in practice

The included **idea-to-sprint** workflow shows what the framework makes possible. It connects clarification, planning, human approval, sprint preparation, implementation, independent review, bounded corrections, reviewed Git closeout, sprint completion, and approved pull-request publication in one governed lifecycle.

{{< thumbcard src="/images/workflows/idea-to-sprint.svg" fit="contain" alt="Idea-to-sprint workflow moving from clarification and human-approved planning through a controlled delivery branch, sprint preparation, independent review, reviewed Git closeout, sprint completion, and pull-request publication" caption="Human authority closes planning and publication; independent review and controlled Git closeout complete delivery." >}}

The parent run provides one end-to-end status and history while keeping planning, delivery, and publication separately inspectable. Completed work remains visible when another step waits, blocks, or needs correction, so recovery starts from the relevant handoff instead of a blank page.

## Reliable delivery includes recovery

Real delivery includes waits, failures, requested changes, and human decisions. Valdr preserves the record that makes those moments actionable:

- Long-running work can pause for an agent, review, child workflow, or human decision and resume after routine interruptions.
- Bounded correction loops keep implementation and review moving without allowing endless retries.
- Failed and blocked steps remain legible, with completed attempts and available evidence preserved.
- Targeted recovery addresses the relevant step without erasing the successful work that came before it.
- Human approvals and rejections remain explicit rather than being inferred from agent output.

Valdr-managed workflow records—including definitions, runs, reviews, evidence, and history—remain in your local workspace until you delete them.

## Start with a working process

The official Valdr Workflow pack gives you included starting points for planning, sprint delivery, task implementation, independent review, correction, closeout, and pull-request publication. Use one as shipped, use **Use as starting point** to create an editable copy in Valdr UI, or compose it into a workflow of your own.

{{< cards >}}
  {{< card link="/valdr/docs/workflows/" title="Start with an included workflow" subtitle="Use a ready-made process for planning, delivery, review, or closeout" icon="play" >}}
  {{< card link="/valdr/docs/ui/workflows/#workflow-builder" title="Adapt it to your team" subtitle="Change steps, routing, context, and authority in the visual workflow builder" icon="adjustments" >}}
  {{< card link="/valdr/docs/workflows/definition-authoring/" title="Standardize how you deliver" subtitle="Create reusable workflows around the decisions, evidence, and standards your work relies on" icon="puzzle" >}}
{{< /cards >}}

{{< cards >}}
  {{< card link="/valdr/docs/ui/workflows/first-workflow/" title="Run Your First Workflow" subtitle="Follow implementation, independent review, and recovery without writing YAML" icon="play" >}}
  {{< card link="/valdr/docs/workflows/idea-to-sprint/" title="See Idea to Sprint" subtitle="Explore its inputs, checkpoints, delivery phases, closeout, and pull-request publication" icon="arrows-expand" >}}
{{< /cards >}}

Go deeper with [How Workflows Run](/valdr/docs/workflows/how-workflows-run/), operate them through the [Workflow UI](/valdr/docs/ui/workflows/), or automate definitions and runs through [`pm_workflow`](/valdr/docs/valdr-mcp/workflows/).