bmad-odoo 1.0.0

package/bmm/workflows/2-plan-workflows/create-odoo-ux-design/steps/step-01-init.md

@@ -0,0 +1,52 @@
+# Bước 1: Xác Định UX Requirements
+
+## 1. Chào Người Dùng
+
+Chào {user_name}! Tôi là Sally, UX Designer Odoo. Tôi sẽ giúp bạn thiết kế UX cho Odoo views.
+
+## 2. Thông Tin UX
+
+### 2.1 Model Cần Thiết Kế
+
+**Model:** {model_name} (ví dụ: sale.order, product.product)
+
+**Mục đích:** {mô tả ngắn}
+
+### 2.2 View Types Cần Thiết Kế
+
+- [ ] Form View - Xem/sửa chi tiết bản ghi
+- [ ] Tree/List View - Danh sách bản ghi
+- [ ] Kanban View - Dạng thẻ
+- [ ] Calendar View - Lịch
+- [ ] Pivot View - Báo cáo pivot
+- [ ] Graph View - Biểu đồ
+- [ ] Search View - Bộ lọc
+
+### 2.3 Người Dùng Mục Tiêu
+
+Ai là người dùng chính của view này?
+- [ ] Quản lý
+- [ ] Nhân viên vận hành
+- [ ] Kế toán
+- [ ] Khác: ___
+
+### 2.4 Tasks Thường Xuyên
+
+Người dùng thường làm gì với view này?
+1. ___
+2. ___
+3. ___
+
+---
+
+## 3. Menu
+
+```
+[C] Tiếp tục
+[H] Trợ giúp về Odoo view types
+[X] Thoát
+```
+
+## 4. Hành Động Tiếp Theo
+
+Khi chọn **[C]**: Tải `steps/step-02-form-design.md`

package/bmm/workflows/2-plan-workflows/create-odoo-ux-design/steps/step-02-form-design.md

@@ -0,0 +1,78 @@
+# Bước 2: Thiết Kế Form View
+
+## 1. Odoo Form View Best Practices
+
+### 1.1 Cấu Trúc Form Chuẩn
+
+```xml
+<form>
+    <header>
+        <!-- Status bar, buttons -->
+        <button name="action_confirm" type="object" string="Xác nhận"/>
+        <field name="state" widget="statusbar"/>
+    </header>
+    <sheet>
+        <div class="oe_title">
+            <!-- Title field -->
+            <h1><field name="name"/></h1>
+        </div>
+        <group>
+            <group>
+                <!-- Left column -->
+            </group>
+            <group>
+                <!-- Right column -->
+            </group>
+        </group>
+        <notebook>
+            <page string="Tab 1">
+                <!-- Content -->
+            </page>
+        </notebook>
+    </sheet>
+    <chatter/>
+</form>
+```
+
+### 1.2 Thiết Kế Form Cho Model: {model}
+
+**Header Section:**
+- Status bar: {các trạng thái}
+- Buttons: {các nút action}
+
+**Title Section:**
+- Field chính: {field_name}
+
+**Main Content (2 columns):**
+
+| Cột trái | Cột phải |
+|----------|----------|
+| {field1} | {field2} |
+| {field3} | {field4} |
+
+**Tabs (Notebook):**
+- Tab 1: {name} - {content}
+- Tab 2: {name} - {content}
+
+### 1.3 Widgets Đề Xuất
+
+| Field | Widget | Lý do |
+|-------|--------|-------|
+| state | statusbar | Hiển thị trạng thái |
+| partner_id | many2one_avatar | Hiển thị avatar |
+| amount | monetary | Format tiền tệ |
+| date | date | Date picker |
+
+---
+
+## 2. Menu
+
+```
+[C] Tiếp tục - Thiết kế Tree View
+[P] Preview - Xem trước XML
+[B] Quay lại
+```
+
+## 3. Hành Động Tiếp Theo
+
+Khi chọn **[C]**: Tải `steps/step-03-tree-design.md`

package/bmm/workflows/2-plan-workflows/create-odoo-ux-design/steps/step-03-tree-design.md

@@ -0,0 +1,84 @@
+# Bước 3: Thiết Kế Tree & Search Views
+
+## 1. Tree View Design
+
+### 1.1 Cấu Trúc Tree View Chuẩn
+
+```xml
+<tree decoration-danger="state == 'cancel'" 
+      decoration-info="state == 'draft'">
+    <field name="name"/>
+    <field name="partner_id"/>
+    <field name="date"/>
+    <field name="amount_total" sum="Total"/>
+    <field name="state" 
+           decoration-success="state == 'done'"
+           widget="badge"/>
+</tree>
+```
+
+### 1.2 Columns Cho Model: {model}
+
+| # | Field | Tên hiển thị | Widget | Optional |
+|---|-------|--------------|--------|----------|
+| 1 | name | Tên | | ✗ |
+| 2 | partner_id | Khách hàng | many2one_avatar | ✗ |
+| 3 | date | Ngày | | ✗ |
+| 4 | state | Trạng thái | badge | ✗ |
+
+### 1.3 Decorations
+
+| Điều kiện | Màu |
+|-----------|-----|
+| state == 'draft' | info (xanh dương) |
+| state == 'done' | success (xanh lá) |
+| state == 'cancel' | danger (đỏ) |
+
+## 2. Search View Design
+
+### 2.1 Cấu Trúc Search View
+
+```xml
+<search>
+    <field name="name"/>
+    <field name="partner_id"/>
+    <filter name="my_records" string="Của tôi" 
+            domain="[('user_id', '=', uid)]"/>
+    <filter name="today" string="Hôm nay" 
+            domain="[('date', '=', context_today())]"/>
+    <group expand="0" string="Group By">
+        <filter name="group_partner" string="Khách hàng" 
+                context="{'group_by': 'partner_id'}"/>
+        <filter name="group_state" string="Trạng thái" 
+                context="{'group_by': 'state'}"/>
+    </group>
+</search>
+```
+
+### 2.2 Filters & Group By
+
+**Quick Filters:**
+| Tên | Domain | Mặc định |
+|-----|--------|----------|
+| Của tôi | [('user_id', '=', uid)] | ✗ |
+| Hôm nay | [('date', '=', context_today())] | ✗ |
+
+**Group By:**
+| Tên | Field |
+|-----|-------|
+| Khách hàng | partner_id |
+| Trạng thái | state |
+
+---
+
+## 3. Menu
+
+```
+[C] Tiếp tục - Hoàn thành
+[K] Kanban - Thiết kế Kanban view
+[B] Quay lại
+```
+
+## 4. Hành Động Tiếp Theo
+
+Khi chọn **[C]**: Tải `steps/step-04-complete.md`

package/bmm/workflows/2-plan-workflows/create-odoo-ux-design/steps/step-04-complete.md

@@ -0,0 +1,55 @@
+# Bước 4: Hoàn Thành UX Design
+
+## 1. Tóm Tắt
+
+```
+🎨 ODOO UX DESIGN
+
+Model: {model_name}
+Views thiết kế:
+├── Form View: ✓
+├── Tree View: ✓
+├── Search View: ✓
+└── Kanban View: {có/không}
+
+Widgets sử dụng: {count}
+Decorations: {count}
+```
+
+## 2. Đầu Ra
+
+### 2.1 File Views XML
+
+Tạo file: `views/{model_name}_views.xml`
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<odoo>
+    <!-- Form View -->
+    <record id="{model}_view_form" model="ir.ui.view">
+        <!-- content -->
+    </record>
+    
+    <!-- Tree View -->
+    <record id="{model}_view_tree" model="ir.ui.view">
+        <!-- content -->
+    </record>
+    
+    <!-- Search View -->
+    <record id="{model}_view_search" model="ir.ui.view">
+        <!-- content -->
+    </record>
+</odoo>
+```
+
+### 2.2 UX Spec
+
+Lưu vào: `{planning_artifacts}/ux-design-{model}.md`
+
+## 3. Bước Tiếp Theo
+
+```
+[1] Thiết kế UX cho model khác
+[2] Tạo addon từ design (workflow create-odoo-addon)
+[X] Quay về menu chính
+```

package/bmm/workflows/2-plan-workflows/create-odoo-ux-design/workflow.md

@@ -0,0 +1,30 @@
+---
+name: create-odoo-ux-design
+description: Thiết kế UX cho Odoo views - forms, trees, kanban theo best practices Odoo.
+web_bundle: true
+---
+
+# Quy Trình Thiết Kế UX Odoo
+
+**Mục tiêu:** Thiết kế UX cho Odoo views theo best practices, bao gồm form views, tree views, và các view types khác.
+
+**Vai trò:** UX Designer chuyên về Odoo với kiến thức về view types và widgets.
+
+---
+
+## KIẾN TRÚC QUY TRÌNH
+
+Quy trình sử dụng **kiến trúc step-file**.
+
+---
+
+## TRÌNH TỰ KHỞI TẠO
+
+### 1. Tải Cấu Hình
+
+Tải config từ {project-root}/_bmad-odoo/bmm/config.yaml
+Tải kiến thức từ {project-root}/_bmad-odoo/bmm/data/odoo-knowledge-base.md
+
+### 2. THỰC THI Bước Đầu Tiên
+
+Tải và thực thi `{project-root}/_bmad-odoo/bmm/workflows/2-plan-workflows/create-odoo-ux-design/steps/step-01-init.md`

package/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md

@@ -0,0 +1,135 @@
+# Step 1: UX Design Workflow Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
+- 📋 YOU ARE A UX FACILITATOR, not a content generator
+- 💬 FOCUS on initialization and setup only - don't look ahead to future steps
+- 🚪 DETECT existing workflow state and handle continuation properly
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- 💾 Initialize document and update frontmatter
+- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until setup is complete
+
+## CONTEXT BOUNDARIES:
+
+- Variables from workflow.md are available in memory
+- Previous context = what's in output document + frontmatter
+- Don't assume knowledge from other steps
+- Input document discovery happens in this step
+
+## YOUR TASK:
+
+Initialize the UX design workflow by detecting continuation state and setting up the design specification document.
+
+## INITIALIZATION SEQUENCE:
+
+### 1. Check for Existing Workflow
+
+First, check if the output document already exists:
+
+- Look for file at `{planning_artifacts}/*ux-design-specification*.md`
+- If exists, read the complete file including frontmatter
+- If not exists, this is a fresh workflow
+
+### 2. Handle Continuation (If Document Exists)
+
+If the document exists and has frontmatter with `stepsCompleted`:
+
+- **STOP here** and load `./step-01b-continue.md` immediately
+- Do not proceed with any initialization tasks
+- Let step-01b handle the continuation logic
+
+### 3. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Input Document Discovery
+
+Discover and load context documents using smart discovery. Documents can be in the following locations:
+- {planning_artifacts}/**
+- {output_folder}/**
+- {product_knowledge}/**
+- docs/**
+
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
+
+Try to discover the following:
+- Product Brief (`*brief*.md`)
+- Research Documents (`*prd*.md`)
+- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
+
+<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
+
+**Loading Rules:**
+
+- Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
+- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
+- index.md is a guide to what's relevant whenever available
+- Track all successfully loaded files in frontmatter `inputDocuments` array
+
+#### B. Create Initial Document
+
+Copy the template from `{installed_path}/ux-design-template.md` to `{planning_artifacts}/ux-design-specification.md`
+Initialize frontmatter in the template.
+
+#### C. Complete Initialization and Report
+
+Complete setup and report to user:
+
+**Document Setup:**
+
+- Created: `{planning_artifacts}/ux-design-specification.md` from template
+- Initialized frontmatter with workflow state
+
+**Input Documents Discovered:**
+Report what was found:
+"Welcome {{user_name}}! I've set up your UX design workspace for {{project_name}}.
+
+**Documents Found:**
+
+- PRD: {number of PRD files loaded or "None found"}
+- Product brief: {number of brief files loaded or "None found"}
+- Other context: {number of other files loaded or "None found"}
+
+**Files loaded:** {list of specific file names or "No additional documents found"}
+
+Do you have any other documents you'd like me to include, or shall we continue to the next step?
+
+[C] Continue to UX discovery"
+
+## NEXT STEP:
+
+After user selects [C] to continue, ensure the file `{planning_artifacts}/ux-design-specification.md` has been created and saved, and then load `./step-02-discovery.md` to begin the UX discovery phase.
+
+Remember: Do NOT proceed to step-02 until output file has been updated and user explicitly selects [C] to continue!
+
+## SUCCESS METRICS:
+
+✅ Existing workflow detected and handed off to step-01b correctly
+✅ Fresh workflow initialized with template and frontmatter
+✅ Input documents discovered and loaded using sharded-first logic
+✅ All discovered files tracked in frontmatter `inputDocuments`
+✅ User confirmed document setup and can proceed
+
+## FAILURE MODES:
+
+❌ Proceeding with fresh initialization when existing workflow exists
+❌ Not updating frontmatter with discovered input documents
+❌ Creating document without proper template
+❌ Not checking sharded folders first before whole files
+❌ Not reporting what documents were found to user
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols

package/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md

@@ -0,0 +1,127 @@
+# Step 1B: UX Design Workflow Continuation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
+- 📋 YOU ARE A UX FACILITATOR, not a content generator
+- 💬 FOCUS on understanding where we left off and continuing appropriately
+- 🚪 RESUME workflow from exact point where it was interrupted
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking action
+- 💾 Keep existing frontmatter `stepsCompleted` values
+- 📖 Only load documents that were already tracked in `inputDocuments`
+- 🚫 FORBIDDEN to modify content completed in previous steps
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter are already loaded
+- Previous context = complete document + existing frontmatter
+- Input documents listed in frontmatter were already processed
+- Last completed step = `lastStep` value from frontmatter
+
+## YOUR TASK:
+
+Resume the UX design workflow from where it was left off, ensuring smooth continuation.
+
+## CONTINUATION SEQUENCE:
+
+### 1. Analyze Current State
+
+Review the frontmatter to understand:
+
+- `stepsCompleted`: Which steps are already done
+- `lastStep`: The most recently completed step number
+- `inputDocuments`: What context was already loaded
+- All other frontmatter variables
+
+### 2. Load All Input Documents
+
+Reload the context documents listed in `inputDocuments`:
+
+- For each document in `inputDocuments`, load the complete file
+- This ensures you have full context for continuation
+- Don't discover new documents - only reload what was previously processed
+
+### 3. Summarize Current Progress
+
+Welcome the user back and provide context:
+"Welcome back {{user_name}}! I'm resuming our UX design collaboration for {{project_name}}.
+
+**Current Progress:**
+
+- Steps completed: {stepsCompleted}
+- Last worked on: Step {lastStep}
+- Context documents available: {len(inputDocuments)} files
+- Current UX design specification is ready with all completed sections
+
+**Document Status:**
+
+- Current UX design document is ready with all completed sections
+- Ready to continue from where we left off
+
+Does this look right, or do you want to make any adjustments before we proceed?"
+
+### 4. Determine Next Step
+
+Based on `lastStep` value, determine which step to load next:
+
+- If `lastStep = 1` → Load `./step-02-discovery.md`
+- If `lastStep = 2` → Load `./step-03-core-experience.md`
+- If `lastStep = 3` → Load `./step-04-emotional-response.md`
+- Continue this pattern for all steps
+- If `lastStep` indicates final step → Workflow already complete
+
+### 5. Present Continuation Options
+
+After presenting current progress, ask:
+"Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
+
+[C] Continue to Step {nextStepNumber}"
+
+## SUCCESS METRICS:
+
+✅ All previous input documents successfully reloaded
+✅ Current workflow state accurately analyzed and presented
+✅ User confirms understanding of progress
+✅ Correct next step identified and prepared for loading
+
+## FAILURE MODES:
+
+❌ Discovering new input documents instead of reloading existing ones
+❌ Modifying content from already completed steps
+❌ Loading wrong next step based on `lastStep` value
+❌ Proceeding without user confirmation of current state
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## WORKFLOW ALREADY COMPLETE?
+
+If `lastStep` indicates the final step is completed:
+"Great news! It looks like we've already completed the UX design workflow for {{project_name}}.
+
+The final UX design specification is ready at {output_folder}/ux-design-specification.md with all sections completed through step {finalStepNumber}.
+
+The complete UX design includes visual foundations, user flows, and design specifications ready for implementation.
+
+Would you like me to:
+
+- Review the completed UX design specification with you
+- Suggest next workflow steps (like wireframe generation or architecture)
+- Start a new UX design revision
+
+What would be most helpful?"
+
+## NEXT STEP:
+
+After user confirms they're ready to continue, load the appropriate next step file based on the `lastStep` value from frontmatter.
+
+Remember: Do NOT load the next step until user explicitly selects [C] to continue!