Software Development Skills

Process a business requirement list (BRL) of any size - tens to thousands of items - into a classified, costed, dependency-ordered implementation plan. For each requirement: 4-way classification (Available-in-Odoo-CE / Available-in-Odoo-EE / Available-in-Viindoo / Custom) via double-profile odoo-semantic-mcp tool calls, a deterministic cost estimate (lookup table, no fabrication), and a requirements traceability matrix (RTM) for consultant export. Runs as a sequential-outer / parallel-inner chunked pipeline with checkpoint/resume so an interrupted session can restart without losing work. Fire ANY time someone pastes or points to a multi-item requirement list to scope end-to-end: "classify these 400 requirements", "turn this RFP spreadsheet into an effort + cost plan".

Generate a structured executive-level inventory of all custom + distribution modules in an Odoo deployment — classifying each as Standard / Distribution-maintained / True custom, surfacing business purpose, base model extended, key custom fields, and upgrade risk flag. Use this skill ANY time a CEO/CTO/PM needs to understand the scope of their Odoo investment, even if they only paste a list of module names. Trigger on: "what have we built on top of Odoo?", "scope of customization before upgrade", "M&A due diligence list our extensions", "what's safe to keep vs deprecate?". Also fires on Vietnamese: "đã tuỳ biến những gì trên Odoo", "phạm vi customization trước khi nâng cấp", "module nào nên giữ module nào nên bỏ". Trigger even if the user dumps a list of names with no context — that's the signal to enumerate. Upgrade risk scoring → odoo-deprecation-audit.

Front-door for ALL Odoo debugging - the moment something is broken, erroring, or behaving wrong, use this BEFORE writing any fix. Runs the scientific method (reproduce -> falsifiable hypothesis -> bisect -> confirm-by-toggle -> regression test) and dispatches specialist debug agents per phase, each at an explicitly chosen model. Fire AGGRESSIVELY on any debug/troubleshoot/diagnose intent even without "debug": a traceback or exception (Expected singleton, AccessError, KeyError, ParseError), "why is X broken/blank/wrong", "not updating", "wrong value", a failed module install/upgrade, a broken screen/widget/console error, or acute "slow right now in production". Vietnamese: "tại sao ... lỗi", "không cập nhật", "view trống", "widget không hiện", "lỗi console". Routing: write the fix via odoo-coding; proactive scans (incl.

Orchestrates a same-series Odoo git rebase - replaying a feature or fix branch onto an updated base of the SAME Odoo major version - forwarding INTENT, not diff text. Pipeline: NL-intake, intent sweep, behavior comparison, outcome classification, design route-out, Plan Mode gate, rebase-onto replay, conflict-resolution loop, range-diff + dup-guard verify, human-confirm gate, and PR. Use when asked to "rebase my branch onto the updated 17.0" or "rebase PR N onto the new base"; "rebase nhánh lên base mới cùng phiên bản" hoặc "cập nhật base cho nhánh feature".

Universal front door for ALL work across 9 personas (CEO/strategist, consultant, sales AE, pre-sales, marketer, developer, QA, customer-success) — brainstorms WHEN intent is vague or open-ended, fast-paths WHEN intent is already clear, and always proposes a plan + gate before execution.

Build a customer-facing pricing proposal for an Odoo deal - license tier recommendation (CE vs EE), implementation cost breakdown, support/maintenance tier, payment terms, optional volume and multi-year discounts, and a clear total with next steps. Accepts customer segment (SME / mid / enterprise), module scope, implementation effort in days (ideally from odoo-gap-analysis output), support SLA tier, and region. Outputs a structured sales document the AE can send or use as a conversation anchor. Trigger on: "draft a pricing proposal", "build a quote", "how much should we charge", "put together a commercial offer", "price breakdown". Vietnamese triggers: "báo giá", "đề xuất giá", "soạn báo giá cho khách", "lập bảng giá cho deal này", "ước tính chi phí cho khách hàng", "đề xuất thương mại".

Version-aware diff of API + feature changes between two Odoo versions, split into a developer track (added/removed/deprecated/changed signatures + migration notes) and a marketer track (business-language highlights). Serves BOTH developer and marketer questions. Resolve the target version from context; if unstated, confirm it. Use ANY time someone compares two Odoo versions: "what changed between these versions", "what's new in Odoo N", "what was removed", era-boundary probes ("when did OWL become default"). Also fires on Vietnamese: "khác nhau giữa hai phiên bản", "có gì mới ở Odoo N", "cái gì bị bỏ đi", "khi nào OWL thành mặc định". When the user asks to audit THEIR code for deprecation (not just see the version-to-version delta), route to odoo-deprecation-audit. When they want marketing-only highlights, route to odoo-feature-highlights.

Catch visual regressions by capturing a screenshot baseline of one Odoo state/build and diffing it against another — before vs after an upgrade, module install, theme change, or code edit. Use when two states must be compared visually and the user wants to know what drifted and how wide the blast radius is. Determinism rule: same login/data/breakpoint/scroll or the diff is noise. Pushy trigger: fire on "compare before and after the upgrade", "screenshot baseline for Odoo", "pixel diff two Odoo builds", "so sánh giao diện trước và sau", "ảnh chụp baseline Odoo".

Generic declarative workflow runner — reads one workflows/ .workflow.yaml file and executes its gated phase sequence according to the declared teampattern (Pipeline, Fan-out/Fan-in, Expert-Pool, Producer-Reviewer, Supervisor, or Hierarchical). Dispatches each phase to a specialist skill via NL description-match, never via the Skill tool. Writes phase artifacts to the outputdir declared in the YAML and checkpoints state for resume.