Menü
Assess Odoo requirement: determine standard vs custom strategy, analyze functional feasibility, produce functional spec. Trigger: Phase 1 (ASSESS) of /odf-new.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | odf-assess |
| description | Assess Odoo requirement: determine standard vs custom strategy, analyze functional feasibility, produce functional spec. Trigger: Phase 1 (ASSESS) of /odf-new. |
| license | MIT |
| metadata | {"author":"adruban","version":"2.0"} |
Use as Phase 1 of /odf-new, after PROPOSE. Determine whether a requirement can be solved with standard Odoo or needs custom development. NEVER write code in this phase — only specs or config guides.
| Rule | Requirement |
|---|---|
| Standard Odoo first | Investigate settings, automated actions, server actions, studio BEFORE considering custom code |
| No code | Produce only specifications (custom) or configuration guides (standard) |
| Version required | Confirm Odoo version before any analysis |
| Requirements numbered | Use REQ-01, REQ-02 format for traceability |
| RFC 2119 | Use MUST/SHALL/SHOULD/MAY in requirements |
| Condition | Action |
|---|---|
| All requirements covered by standard | strategy: standard. Produce step-by-step config guide. next_recommended: [] |
| Any gap exists | strategy: custom. Produce functional spec for gaps only. next_recommended: ["design"] |
mem_save(title: "odf/{change}/assess", ...)Return ODF Result envelope with: status (ok), executive_summary, strategy (standard|custom), artifacts_saved, next_recommended (["design"] or []), risks, odoo_version, modules_affected.
/home/adruban/.config/opencode/skills/_shared/result-contract.md — ODF Result envelope/home/adruban/.config/opencode/skills/_shared/odoo-sources.md — Local source pathsImplement Odoo tasks from design artifact. Write code following spec + design. Trigger: Phase 3 (IMPLEMENT) of /odf-new after DESIGN approved.
Detect + persist Odoo project context: version, modules, test runner, lint tools, conventions. Trigger: /odf-init, first time in a project.
Quality gate for ODF: evidence-based risk tiers (0/1/4 lenses), spec compliance matrix, single-attempt correction budget. Trigger: Phase 4 (VERIFY) of /odf-new.
Create an ODF change proposal with business context, scope, and approach. Trigger: Phase 0 (PROPOSE) of /odf-new.
Strict TDD mode for ODF: tests before code. Two-source kill switch (global + local), any off wins, fail-closed. Trigger: /odf-tdd on, effective TDD mode active, or when strict TDD enforcement is needed.
Deep investigation of Odoo codebase to understand patterns before proposing solutions. Trigger: /odf-explore, 'how does Odoo handle X', research, investigation.