ODF Agent Team

Spec-driven Odoo delivery on OpenCode — a stage pipeline, 11 specialized agents, 51 skills, and deterministic CLIs so your AI team finds the codebase instead of inventing it.

ODF — spec-driven Odoo delivery on OpenCode. Turns a generic AI assistant into a structured Odoo delivery team. An orchestrator routes every stage through a plugin that resolves the right agent, injects at most five skill rules, enforces Policy Gates, and seals evidence — so nothing ships on a guess.

odf-delegation plugin ──► task() ──► specialist agent ──► Odoo worktree
        │                                                          │
   registry · skills · gates                                tests · lint · refs

Quickstart

# 1. Install into ~/.config/opencode (release-pinned)
curl -fsSL https://raw.githubusercontent.com/antoniodavid/odf-agent-team/v1.6.2/install.sh | BRANCH=v1.6.2 bash

# 2. Inside OpenCode, from any Odoo worktree:
/odf-init           # detect version, modules, test runner
/odf-new my-feature # preflight → DECIDE → PLAN → BUILD → VERIFY

Need CodeGraph structural queries? Add -- --with-codegraph. Non-interactive CI? Add -- --yes.

How it works

init → health/preflight → one resolved route → only its required stages → archive when applicable

The user sees one route selected by work_type; micro/standard/full is entry triage, not another workflow. Small changes and the default feature-inline route use DECIDE → BUILD → VERIFY with inline QA, where feature-inline runs one bounded ASSESS only when the deterministic entry gate selects assess; bugfixes use FIX → BUILD → VERIFY with inline regression QA; complex/high-risk routes use formal PLAN/QA-PLAN. After the gate and approved Expectations, one bounded Context Manifest is built and forwarded unchanged to ASSESS and BUILD. The shadow prediction is advisory and does not alter execution. Full vocabulary: docs/architecture.md · route matrix: docs/route-contract.md.