---
title: Agentic Workflows
description: Standalone adoption lane for tracked OAT projects, workflow lifecycle execution, ideas, and workflow-oriented skills.
---

# Agentic Workflows

Agentic Workflows is the OAT lane for tracked, resumable work on top of the base CLI and provider-sync layers.

Use this section when you want explicit project artifacts, stable task IDs, review loops, and resumable execution across longer-running work. The workflow layer is optional; stay with direct CLI usage when the task is straightforward and the overhead of project artifacts would outweigh the value.

## Contents

- [Ideas Workflow](ideas/index.md) - Lightweight idea capture, brainstorming, and promotion into tracked projects when the work becomes concrete.
- [Workflow & Projects](projects/index.md) - Lifecycle, artifacts, reviews, PR flow, and repository analysis.
- [Wave Workflows](wave-workflows.md) - Program-level coordination for executing a corpus of external plans as ordered wrapper projects.
- [Skills](skills/index.md) - Workflow-oriented skill discovery and use-case routing.

## What This Section Is

This section explains when workflow mode is worth the overhead, how OAT projects move through lifecycle phases, and how ideas, skills, reviews, and PR flow fit into that model.

## Who It's For

- Teams doing multi-session or multi-phase work that benefits from tracked artifacts
- Users who want explicit discovery, planning, implementation, and review state
- Repos that need a repeatable human-in-the-loop execution model

## When To Use Workflow Mode

Use workflow mode when:

- the work spans multiple sessions or contributors
- you want explicit discovery, plan, implementation, and review artifacts
- you need stable task sequencing and resumable execution
- you want human-in-the-loop checkpoints around risky transitions

Stay with direct CLI usage when:

- the task is straightforward and bounded
- you mainly need provider sync or a utility command
- the overhead of project artifacts would outweigh the value

## Workflow Modes In Practice

- CLI only: direct commands, no tracked project artifacts
- Quick mode: tracked work with a lighter upfront planning path
- Spec-driven mode: explicit discovery, requirements, design, and plan artifacts
- Import mode: an externally-authored plan imported into OAT for tracked execution

## Start Here

- Use [Skills](skills/index.md) when you want task-oriented guidance on the most useful workflow skills.
- Go to [Workflow & Projects](projects/index.md) when you need the lifecycle and artifact model in detail.
- Use [Ideas](ideas/index.md) when the work is still exploratory.

## Common Tasks

- Capture or refine early work in [Ideas](ideas/index.md).
- Understand how tracked projects progress in [Workflow & Projects](projects/index.md).
- Learn the artifact contract in [Artifacts](projects/artifacts.md).
- Understand review and PR expectations in [Reviews](projects/reviews.md) and [PR Flow](projects/pr-flow.md).

## Go Deeper

- [Skills](skills/index.md) - Workflow-oriented skill discovery and use-case routing.
- [Ideas](ideas/index.md) - Idea capture, refinement, and promotion flows.
- [Workflow & Projects](projects/index.md) - Lifecycle, artifacts, reviews, PR flow, and repository analysis.
