fhidalgodev/dsh-odoo-sdd

dsh-odoo-sdd is a native plugin published on npm as dsh-odoo-sdd under the MIT license, and its entire purpose is to turn DeepSeek Harness into a closed-loop, specification-driven development pipeline for Odoo modules. It mounts into DSH as a Cordis bundle and consumes the host's tools service, so the runtime requires DSH ≥ 0.1.2-rc.1 sitting on Node ≥ 20. The plugin never starts Docker, never spawns odoo-bin, and never invents credentials: instead it points at an Odoo instance the developer already runs (dev or staging) through a gitignored .env and speaks plain JSON-RPC against it.

The workflow is a five-phase SDD protocol with fail-closed gates: CLARIFY holds an interview plus security questions, READ_SPEC freezes an immutable spec.md, ARCHITECTURE drafts models, views, security rules and a test plan, WRITE_CODE emits module sources plus OCA-style docs, and VERIFY installs the module on the live server, reads the real traceback, and iterates fixes. Each transition requires an explicit APPROVED marker, three consecutive failures force a root-cause diagnosis, verify/fix loops are capped, a stop.md halts everything, and a failed verification is persisted as FAILED so it can never silently turn into success. The target users are Odoo developers, architects and reviewers who want spec, architecture, code and verification traced end-to-end on a real server.

Hard dependencies are DSH ≥ 0.1.2-rc.1, Node ≥ 20, an existing Odoo instance reachable over HTTP(S), and a disposable dev/staging database that verification is allowed to write into; an optional Playwright browser tool covers only the UI layer of verification, and without it those scenarios are simply marked for manual checking. The plugin never writes a git commit and never asks for a password over chat. Releases are immutable on npm, built automatically by the prepack hook, and after the first manual npm publish they are driven by GitHub Releases through .github/workflows/publish.yml, which validates tag, version and provenance, refuses a duplicate version, and uses npm's OIDC trusted publishing so no NPM_TOKEN has to live in the repository.