Odoo feature planning
Use for new features, broad refactors, or tasks with unresolved business rules. For a small, unambiguous change, keep planning brief and proceed; do not force a lengthy interview.
Steps
- Inspect the repository and relevant addon first: Odoo version/edition, module conventions, models, views, security, integrations, tests, and existing behavior.
- State the problem and observable acceptance criteria in user terms. Ask focused questions only for decisions that materially affect behavior, data, security, or compatibility. Otherwise name conservative assumptions.
- Explore one or two viable designs when there is a real tradeoff. Consider ORM ownership, access control, multi-company, data compatibility, user experience, and upgrade implications.
- Recommend the smallest design that meets the criteria. Avoid speculative generalization, unnecessary dependencies, and unrelated cleanup.
- Write an implementation sequence with affected files/components and a validation plan. Include test cases, install/update checks, and any migration/rollout risks.
- For consequential architecture or data changes, present the plan for user agreement before editing. For straightforward contained work, state the plan and execute.
- After implementation, compare results against each acceptance criterion and report checks actually run.
Planning is a communication aid, not a requirement to stop for approval on every low-risk coding task.
1---2name: odoo-feature-planning3description: Clarify and design non-trivial Odoo features or refactors before editing code, with concise requirements, architecture, and test plans.4metadata:5 source: https://skillmd.com/skills/shone-navabrind/odoo-feature-planning6---78# Odoo feature planning910Use for new features, broad refactors, or tasks with unresolved business rules. For a small, unambiguous change, keep planning brief and proceed; do not force a lengthy interview.1112## Steps13141. Inspect the repository and relevant addon first: Odoo version/edition, module conventions, models, views, security, integrations, tests, and existing behavior.152. State the problem and observable acceptance criteria in user terms. Ask focused questions only for decisions that materially affect behavior, data, security, or compatibility. Otherwise name conservative assumptions.163. Explore one or two viable designs when there is a real tradeoff. Consider ORM ownership, access control, multi-company, data compatibility, user experience, and upgrade implications.174. Recommend the smallest design that meets the criteria. Avoid speculative generalization, unnecessary dependencies, and unrelated cleanup.185. Write an implementation sequence with affected files/components and a validation plan. Include test cases, install/update checks, and any migration/rollout risks.196. For consequential architecture or data changes, present the plan for user agreement before editing. For straightforward contained work, state the plan and execute.207. After implementation, compare results against each acceptance criterion and report checks actually run.2122Planning is a communication aid, not a requirement to stop for approval on every low-risk coding task.