القائمة
Create technical design + task breakdown for Odoo custom module. Trigger: Phase 2 (DESIGN) of /odf-new after ASSESS approved.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Implement 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.
| name | odf-design |
| description | Create technical design + task breakdown for Odoo custom module. Trigger: Phase 2 (DESIGN) of /odf-new after ASSESS approved. |
| license | MIT |
| metadata | {"author":"adruban","version":"2.0"} |
Use after ASSESS returns strategy: custom. Produce architecture decisions, data model, file structure, and phased task breakdown. The orchestrator will approve before IMPLEMENT.
| Rule | Requirement |
|---|---|
| Read source first | Read the Odoo module being extended BEFORE designing |
| Traceability | Every task must link to a requirement REQ-XX from ASSESS |
| Security required | Every new model MUST have ir.model.access.csv |
| Tests required | Every feature MUST have at least one test task |
| OCA conventions | File structure, naming, manifest follow OCA standards |
| Condition | Action |
|---|---|
| Single module | Design one module with 3 phases: Foundation → Views → Tests |
| Multi-module (2+) | Design per module: Primary first (all phases), then secondary. Prefix task IDs (A1.1, B1.1) |
| Complex architecture | Include architecture decisions with rationale + rejected alternatives |
mem_get_observation(id) on assess artifact from Engrammem_save(title: "odf/{change}/design", ...)Return ODF Result envelope with: status (ok), executive_summary ("N models, N views, N tasks in M phases"), artifacts_saved, next_recommended (["implement"]), 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 paths