Ouro Ouroboros

requirements

Overview

Creates, updates, or discusses .ouro/requirements.md. The command supports three subcommands:

  • create converts Markdown/DOCX/PDF inputs into a requirements baseline.
  • refine merges new requirement drafts into the existing file.
  • talk records spoken interviews, transcribes them, and appends the summary to the requirements file.

Usage

ouro requirements create <input.(md|docx|pdf)> [--human] [--agent-model <model>] [--codex-model <model>] [--max-questions <n>]
ouro requirements refine <input.(md|docx|pdf)> [--human] [--agent-model <model>] [--codex-model <model>] [--max-questions <n>]
ouro requirements talk [--max-questions <n>] <output.md>

Key Options

  • --human – Disable Codex auto-responses during facilitator Q&A.
  • --agent-model <model> – Override the agent used for drafting or refining requirements.
  • --codex-model <model> – Override Codex when answering facilitator questions automatically.
  • --max-questions <n> – Set the maximum facilitator turns for create/refine; limits the number of listening windows for talk when provided.

Inputs & Outputs

  • create/refine inputs: Markdown or rich text (DOCX/PDF converted via pandoc) containing requirement notes.
  • talk inputs: live audio captured through the configured recorder; optional existing Markdown to sync before the session.
  • Outputs: updates .ouro/requirements.md, optionally generating appendices, facilitator Q&A, and summaries.

When to Use

  • Establish a living requirements document sourced from interviews, specs, or workshops.
  • Keep requirements aligned with product discovery sessions captured via talk.

Follow-up Checklist

  • Ensure pandoc is installed when working with DOCX/PDF inputs.
  • Commit the requirements update and re-run ouro compile so agent documentation reflects the latest scope.