Menú
QA workflow for ODF: test planning, coverage analysis, test review, quality gates. Trigger: /odf-qa or orchestrator needs QA in any phase.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | odf-qa |
| description | QA workflow for ODF: test planning, coverage analysis, test review, quality gates. Trigger: /odf-qa or orchestrator needs QA in any phase. |
| license | MIT |
| metadata | {"author":"adruban","version":"2.0"} |
Use for test strategy planning (after ASSESS), test review (during IMPLEMENT), coverage aggregation (before VERIFY), or final QA reporting (after VERIFY).
| Rule | Requirement |
|---|---|
| Run actual coverage | Use coverage tools — don't estimate coverage percentages |
| Trace to requirements | Every test must map to a REQ-XX from the assess artifact |
| Flag untested paths | Identify critical paths without test coverage — don't ignore them |
| Check isolation | Tests MUST use TransactionCase — no shared state between tests |
| Phase | Input | Output |
|---|---|---|
| QA-PLAN | Assess artifact | Test scenarios (unit/integration/E2E) + coverage targets + fixture design |
| QA-REVIEW | Test files from IMPLEMENT | Test quality report (isolation, assertions, coverage delta) |
| QA-AGGREGATE | All batch results | Aggregate coverage report + requirements traceability |
| QA-REPORT | All QA artifacts | Final QA metrics + quality gate status + verdict |
Return ODF Result envelope with: status (ok|warning|blocked|failed), executive_summary ("{N} tests, {X}% coverage, {Y}/{Z} requirements covered"), artifacts_saved (qa-plan, qa-review, qa-aggregate, qa-report), next_recommended (["implement"] or ["verify"]), 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.