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.
The thin spine — one resolved route decides which stages run
Routes: feature-inline · small-change · bugfix ·
feature · cross-domain · migration ·
security · verify-only ·
full matrix →
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.
Every link is a page
Twenty-five documentation sources render as pages with a grouped sidebar, in-page TOC, breadcrumbs, prev/next, reading time, and the search palette.
Markdown links are rewritten at build time, so no documentation link points at a raw .md file.
No personal paths in the pack
Both installers rewrite any /home/<user>/.config/opencode, skill metadata uses the project handle, and the timesheet binary is rebuilt with -trimpath.
Internal task logs and SDD state use $HOME or a relative root.
A privacy test that fails the build
Twenty-nine assertions scan the published surface for home paths, provider emails, private keys, token formats, URL credentials, and literal passwords.
docs:check keeps every generated page in sync.
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.
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 BUILDassess— redundancy, an existing surface, or--assessruns one bounded assessmentescalate— risk signals keep the formal DECIDE → PLAN route
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 · delegationA 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
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 · evaluationRouting 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 · activationScoped 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 activationThe 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
The gate reads skip (terminal decision), assess (one bounded ASSESS), or escalate (formal feature route).
bugfix
focused fix · inline regression QA
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
Cross-domain BUILD runs isolated branches with one aggregate join, one commit, and one receipt on failure.
native delegation
one visible child per unit
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.
Frontmatter parses, name matches its directory, descriptions stay within 1024 characters, and every path stays inside the pack.
150–600 characters, complete sentences, no ASCII banners, no truncated tails, and no duplicated rule sets across skills.
Score ties break by registry order, not prompt length; a delegation still carries at most five compact rules.
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 →Start using ODF
Mental model, entry commands, routes, activation, and how to read a stop.
Intended usage routeRoutes & gates
Every work type, stage, canonical artifact, completion rule, and gate.
Route contract understandUnderstand the system
Stages, components, persistence roles, and data flow.
Architecture extendExtend the plugin
The 29 runtime tools, modules, native delegation, and the odf_delegate path.
Plugin reference contributeWrite a skill
Structure, frontmatter, the compact-rule contract, and validation.
Style guide measureMeasure routing quality
Decision-quality report, local reviews, agreement, cadence, and proposals.
Decision evaluationSee the system
Open on Pages ↗Phase flow & routing
Full pipeline, fast routes, and how work reaches the right agent.
Open diagramHarness architecture
Operator → orchestrator → plugin → fleet → Odoo worktree.
Open diagramOne-call efficiency
ODF's single round-trip vs the naive grep-and-read context loop.
Open diagramContracts & operations
- Metrics & Engram maintenance — evaluation commands, retention, prune
- Decision evaluation — decision-quality report, reviews, cadence
- Skill validation —
npm run validate:skills - Development — 1405 unit + 331 YAML + 18 harness tests
- Archive — completed roadmaps and plans
- Press / anywhere to search everything above