ODF docs
GitHub ↗

spec-driven Odoo delivery on OpenCode · v1.6.2

Ship Odoo changes with evidence, not guesses.

ODF turns OpenCode into a structured Odoo delivery team — 87 validated skills, 12 agents, 29 plugin tools, and policy gates that run before your specialist writes a line.

87validated skills
11agents
23commands
29plugin tools
1405unit tests
331YAML scenarios

What's new in 1.6.2

Full changelog →

The documentation became a real website — every link opens a styled page — and the shipped pack stopped carrying personal paths.

1.6.1 highlights

Full changelog →

Thirty-six merged commits since 1.6.0: a leaner default route, one bounded context artifact, a delegation lifecycle that survives cancellation and expiry, stops that name their continuation, and a decision-quality loop.

1.6.1 · route

Feature-inline with a real gate

The default standard-feature route is DECIDE → BUILD → VERIFY, and DECIDE is deterministic:

  • skip — clear intent binds a terminal decision before BUILD
  • assess — redundancy, an existing surface, or --assess runs one bounded assessment
  • escalate — risk signals keep the formal DECIDE → PLAN route
Route matrix
1.6.1 · context

One Context Manifest, forwarded unchanged

The entry builds a bounded, reference-only manifest — project facts, references, redundancy counts, gate decision, Expectations ref — and forwards the same bytes to ASSESS and BUILD.

Its digest covers every field; redundancy gates the route instead of interrogating the user.

Context contract
1.6.1 · delegation

A lifecycle that survives reality

Prepare → launch → seal binds the child to parent, agent, model, workspace, and prompt digest.

  • Parent cancellation aborts the child and settles the attempt
  • Expired tokens recover through one single-use late-seal capability
  • Every mismatch reports its exact seal reason
Delegation lifecycle
1.6.1 · safety

Stops that name their continuation

Every blocked or failed envelope carries a stop_disposition: safety, human decision, repairable, dependency, terminal, or unclassified.

Unknown reasons fail closed instead of auto-continuing.

Stopping safely
1.6.1 · evaluation

Routing quality you can measure

Golden trajectories, a decision-quality report, local human reviews, human/judge agreement, period comparison, review cadence, and improvement proposals.

A missing judge verdict is unavailable — never agreement.

Decision evaluation
1.6.1 · activation

Scoped to initialized projects

.odf/project.json marks a project as initialized and keeps the first activation timestamp across re-scans.

Activation after runtime boot prints the exact reload requirement instead of suggesting a reinstall.

Project activation

The flows

Route contract →

One route per change; the orchestrator shows the route, not every adapter. Amber marks a gate, plum a stage where work is written.

feature-inline default standard feature · inline plan
Entry + Context Manifest→ DECIDE gate→ BUILD→ VERIFY→ ARCHIVE

The gate reads skip (terminal decision), assess (one bounded ASSESS), or escalate (formal feature route).

bugfix focused fix · inline regression QA
Entry→ FIX · diagnose→ BUILD→ VERIFY→ ARCHIVE

Small changes follow the same shape from DECIDE. Neither needs a formal plan artifact.

feature · cross-domain · migration · security formal plan · parallel BUILD when cross-domain
Entry + Context Manifest→ DECIDE→ PLAN→ BUILD · 2–3 branches→ VERIFY→ ARCHIVE

Cross-domain BUILD runs isolated branches with one aggregate join, one commit, and one receipt on failure.

native delegation one visible child per unit
PREPARE · token→ LAUNCH · child session→ SEAL · gates + evidence

Cancel propagates to the child; an expired token recovers through late_seal_prepare → seal with a ten-minute capability.

Skill quality, enforced

Skill style guide →

1.6.1 treats a skill's compact rules as a product surface. All 87 skills are checked against the Agent Skills format, and every rule was regenerated from the skill's own content.

Spec validation

Frontmatter parses, name matches its directory, descriptions stay within 1024 characters, and every path stays inside the pack.

Compact-rule contract

150–600 characters, complete sentences, no ASCII banners, no truncated tails, and no duplicated rule sets across skills.

Deterministic selection

Score ties break by registry order, not prompt length; a delegation still carries at most five compact rules.

$ npm run validate:skills
ODF skill validation: 87 skills
✅ errors: 0

CI runs the validator alongside typecheck, unit tests, YAML scenarios, and registry validation. Adding a skill? Start at the style guide.

I want to…

Full index →

See the system

Open on Pages ↗

Contracts & operations

Running the pack