Aigon organises development work into three workflows, each with its own lifecycle.

Three workflows

Features

The core delivery workflow. A feature moves through: create → prioritise → start → implement → evaluate → close. Features produce code that gets merged to your main branch.

Features support all four execution modes — Drive, Fleet, Autopilot, and Swarm.

Features can declare dependencies on other features using depends_on in the spec’s Dependencies section. When you prioritise a feature, Aigon resolves dependency references and checks for circular dependencies. Dependent features cannot be started until their dependencies are done.

Research

The discovery workflow. Research topics move through: create → prioritise → start → investigate → evaluate → close. Research produces findings and recommendations that feed into feature creation.

Research supports Drive (one agent), Fleet (multiple agents for diverse perspectives), and Autopilot (research-autopilot — hands-off Fleet that auto-evaluates). Research findings are synthesised qualitatively rather than scored.

Feedback

The triage workflow. Feedback items move through: create → triage → promote/reject → close. Feedback captures user input, bugs, and improvement ideas. Triaged feedback can be promoted to a feature or research topic.

Feedback does not use agents or execution modes — it’s a lightweight categorisation workflow.

Four execution modes

Modes apply to features (all four) and research (Drive, Fleet, and Autopilot).

In Fleet mode, agents compete in isolated worktrees on the same spec. You evaluate and merge the winner:

See Execution Modes for details.

Three surfaces

You interact with Aigon through three interchangeable surfaces:

• Slash commands — inside an agent session (/aigon:feature-start 42)
• CLI — from any terminal (aigon feature-start 42)
• Dashboard — browser UI at aigon.localhost (click “Start” on a card)

All three drive the same underlying state. Mix them freely.

Specs as folders

Each spec file lives in a folder that reflects its current stage. As you run commands, Aigon moves the file through the pipeline:

docs/specs/features/
  01-inbox/        → ideas
  02-backlog/      → prioritised, assigned an ID
  03-in-progress/  → being worked on
  04-in-evaluation/→ comparing implementations (Fleet)
  05-done/         → merged and complete

Research and feedback follow the same pattern with their own folder structures. See File Structure for the full layout.