Ouro Ouroboros

agent

Overview

Provides composite agent-powered workflows. The current subcommand, flux, assembles a repository snapshot (file tree, ontology, requirements, docs map, curated snippets) and asks an agent to produce a roadmap-style report.

Usage

ouro agent flux [--skip-gather] [--agent-model <model>] [--max-questions <n>] [--max-tree-entries <n>] \
                [--max-snippets <n>] [--snippet-lines <n>] [--output <path>]

Key Options

  • --skip-gather – Avoid running ouro gather before context assembly.
  • --agent-model <model> – Override the model that plans the flux roadmap.
  • --max-questions <n> – Limit facilitator turns (default 8).
  • --max-tree-entries <n> – Cap the number of paths in the file tree preview (default 240).
  • --max-snippets <n> / --snippet-lines <n> – Control how many source excerpts and how many lines per excerpt are embedded in the prompt.
  • --output <path> – Write the Markdown report somewhere other than .ouro/flux/report.md.

Inputs & Outputs

  • Inputs: repository knowledge files, optional fresh gather results, targeted code snippets collected directly from disk.
  • Outputs: Markdown report summarising the project and task backlog, written via writeTextIfChanged so reruns do not cause unnecessary churn.

When to Use

  • Produce a shareable status snapshot before planning a feature or refactor.
  • Supply onboarding material to human teammates or downstream agents.

Follow-up Checklist

  • Review the generated roadmap and convert tasks into issue tracker items.
  • Regenerate after significant code or ontology changes to keep the flux report fresh.