bmad-odoo 1.0.0

package/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md

@@ -0,0 +1,106 @@
+---
+name: 'step-05-adversarial-review'
+description: 'Construct diff and invoke adversarial review task'
+
+workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev'
+thisStepFile: '{workflow_path}/steps/step-05-adversarial-review.md'
+nextStepFile: '{workflow_path}/steps/step-06-resolve-findings.md'
+---
+
+# Step 5: Adversarial Code Review
+
+**Goal:** Construct diff of all changes, invoke adversarial review task, present findings.
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+- `{baseline_commit}` - Git HEAD at workflow start (CRITICAL for diff)
+- `{execution_mode}` - "tech-spec" or "direct"
+- `{tech_spec_path}` - Tech-spec file (if Mode A)
+
+---
+
+### 1. Construct Diff
+
+Build complete diff of all changes since workflow started.
+
+### If `{baseline_commit}` is a Git commit hash:
+
+**Tracked File Changes:**
+
+```bash
+git diff {baseline_commit}
+```
+
+**New Untracked Files:**
+Only include untracked files that YOU created during this workflow (steps 2-4).
+Do not include pre-existing untracked files.
+For each new file created, include its full content as a "new file" addition.
+
+### If `{baseline_commit}` is "NO_GIT":
+
+Use best-effort diff construction:
+
+- List all files you modified during steps 2-4
+- For each file, show the changes you made (before/after if you recall, or just current state)
+- Include any new files you created with their full content
+- Note: This is less precise than Git diff but still enables meaningful review
+
+### Capture as {diff_output}
+
+Merge all changes into `{diff_output}`.
+
+**Note:** Do NOT `git add` anything - this is read-only inspection.
+
+---
+
+### 2. Invoke Adversarial Review
+
+With `{diff_output}` constructed, invoke the review task. If possible, use information asymmetry: run this step, and only it, in a separate subagent or process with read access to the project, but no context except the `{diff_output}`.
+
+```xml
+<invoke-task>Review {diff_output} using {project-root}/_bmad/core/tasks/review-adversarial-general.xml</invoke-task>
+```
+
+**Platform fallback:** If task invocation not available, load the task file and execute its instructions inline, passing `{diff_output}` as the content.
+
+The task should: review `{diff_output}` and return a list of findings.
+
+---
+
+### 3. Process Findings
+
+Capture the findings from the task output.
+**If zero findings:** HALT - this is suspicious. Re-analyze or request user guidance.
+Evaluate severity (Critical, High, Medium, Low) and validity (real, noise, undecided).
+DO NOT exclude findings based on severity or validity unless explicitly asked to do so.
+Order findings by severity.
+Number the ordered findings (F1, F2, F3, etc.).
+If TodoWrite or similar tool is available, turn each finding into a TODO, include ID, severity, validity, and description in the TODO; otherwise present findings as a table with columns: ID, Severity, Validity, Description
+
+---
+
+## NEXT STEP
+
+With findings in hand, load `step-06-resolve-findings.md` for user to choose resolution approach.
+
+---
+
+## SUCCESS METRICS
+
+- Diff constructed from baseline_commit
+- New files included in diff
+- Task invoked with diff as input
+- Findings received
+- Findings processed into TODOs or table and presented to user
+
+## FAILURE MODES
+
+- Missing baseline_commit (can't construct accurate diff)
+- Not including new untracked files in diff
+- Invoking task without providing diff input
+- Accepting zero findings without questioning
+- Presenting fewer findings than the review task returned without explicit instruction to do so

package/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md

@@ -0,0 +1,140 @@
+---
+name: 'step-06-resolve-findings'
+description: 'Handle review findings interactively, apply fixes, update tech-spec with final status'
+
+workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev'
+thisStepFile: '{workflow_path}/steps/step-06-resolve-findings.md'
+---
+
+# Step 6: Resolve Findings
+
+**Goal:** Handle adversarial review findings interactively, apply fixes, finalize tech-spec.
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+- `{baseline_commit}` - Git HEAD at workflow start
+- `{execution_mode}` - "tech-spec" or "direct"
+- `{tech_spec_path}` - Tech-spec file (if Mode A)
+- Findings table from step-05
+
+---
+
+## RESOLUTION OPTIONS
+
+Present choice to user:
+
+```
+How would you like to handle these findings?
+
+**[1] Walk through** - Discuss each finding individually
+**[2] Auto-fix** - Automatically fix issues classified as "real"
+**[3] Skip** - Acknowledge and proceed to commit
+```
+
+---
+
+## OPTION 1: WALK THROUGH
+
+For each finding in order:
+
+1. Present the finding with context
+2. Ask: **fix now / skip / discuss**
+3. If fix: Apply the fix immediately
+4. If skip: Note as acknowledged, continue
+5. If discuss: Provide more context, re-ask
+6. Move to next finding
+
+After all findings processed, summarize what was fixed/skipped.
+
+---
+
+## OPTION 2: AUTO-FIX
+
+1. Filter findings to only those classified as "real"
+2. Apply fixes for each real finding
+3. Report what was fixed:
+
+```
+**Auto-fix Applied:**
+- F1: {description of fix}
+- F3: {description of fix}
+...
+
+Skipped (noise/uncertain): F2, F4
+```
+
+---
+
+## OPTION 3: SKIP
+
+1. Acknowledge all findings were reviewed
+2. Note that user chose to proceed without fixes
+3. Continue to completion
+
+---
+
+## UPDATE TECH-SPEC (Mode A only)
+
+If `{execution_mode}` is "tech-spec":
+
+1. Load `{tech_spec_path}`
+2. Update status to "Completed"
+3. Add review notes:
+   ```
+   ## Review Notes
+   - Adversarial review completed
+   - Findings: {count} total, {fixed} fixed, {skipped} skipped
+   - Resolution approach: {walk-through/auto-fix/skip}
+   ```
+4. Save changes
+
+---
+
+## COMPLETION OUTPUT
+
+```
+**Review complete. Ready to commit.**
+
+**Implementation Summary:**
+- {what was implemented}
+- Files modified: {count}
+- Tests: {status}
+- Review findings: {X} addressed, {Y} skipped
+
+{Explain what was implemented based on user_skill_level}
+```
+
+---
+
+## WORKFLOW COMPLETE
+
+This is the final step. The Quick Dev workflow is now complete.
+
+User can:
+
+- Commit changes
+- Run additional tests
+- Start new Quick Dev session
+
+---
+
+## SUCCESS METRICS
+
+- User presented with resolution options
+- Chosen approach executed correctly
+- Fixes applied cleanly (if applicable)
+- Tech-spec updated with final status (Mode A)
+- Completion summary provided
+- User understands what was implemented
+
+## FAILURE MODES
+
+- Not presenting resolution options
+- Auto-fixing "noise" or "uncertain" findings
+- Not updating tech-spec after resolution (Mode A)
+- No completion summary
+- Leaving user unclear on next steps

package/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md

@@ -0,0 +1,52 @@
+---
+name: quick-dev
+description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
+---
+
+# Quick Dev Workflow
+
+**Goal:** Execute implementation tasks efficiently, either from a tech-spec or direct user instructions.
+
+**Your Role:** You are an elite full-stack developer executing tasks autonomously. Follow patterns, ship code, run tests. Every response moves the project forward.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for focused execution:
+
+- Each step loads fresh to combat "lost in the middle"
+- State persists via variables: `{baseline_commit}`, `{execution_mode}`, `{tech_spec_path}`
+- Sequential progression through implementation phases
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `user_name`, `communication_language`, `user_skill_level`
+- `output_folder`, `planning_artifacts`,  `implementation_artifacts`
+- `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Paths
+
+- `installed_path` = `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev`
+- `project_context` = `**/project-context.md` (load if exists)
+- `project_levels` = `{project-root}/_bmad/bmm/workflows/workflow-status/project-levels.yaml`
+
+### Related Workflows
+
+- `create_tech_spec_workflow` = `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml`
+- `workflow_init` = `{project-root}/_bmad/bmm/workflows/workflow-status/init/workflow.yaml`
+- `party_mode_exec` = `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
+- `advanced_elicitation` = `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml`
+
+---
+
+## EXECUTION
+
+Load and execute `steps/step-01-mode-detection.md` to begin the workflow.

package/bmm/workflows/document-odoo/steps/step-01-init.md

@@ -0,0 +1,43 @@
+# Bước 1: Xác Định Tài Liệu Cần Tạo
+
+## 1. Chào Người Dùng
+
+Chào {user_name}! Tôi là Paige, Technical Writer Odoo. Tôi sẽ giúp bạn tạo tài liệu cho Odoo module.
+
+## 2. Thông Tin Module
+
+### 2.1 Module Cần Tài Liệu
+
+**Module name:** ___
+
+**Đường dẫn:** {odoo.customModulesPath}/___
+
+### 2.2 Loại Tài Liệu Cần Tạo
+
+- [ ] README.rst (Mô tả module) - **Bắt buộc cho OCA**
+- [ ] User Guide (Hướng dẫn sử dụng)
+- [ ] API Documentation (Tài liệu API)
+- [ ] Installation Guide (Hướng dẫn cài đặt)
+- [ ] Changelog (Lịch sử thay đổi)
+
+### 2.3 Đối Tượng Đọc
+
+Tài liệu này dành cho ai?
+- [ ] End Users (Người dùng cuối)
+- [ ] Administrators (Quản trị viên)
+- [ ] Developers (Lập trình viên)
+- [ ] IT Support (Hỗ trợ kỹ thuật)
+
+---
+
+## 3. Menu
+
+```
+[C] Tiếp tục
+[H] Trợ giúp về chuẩn OCA docs
+[X] Thoát
+```
+
+## 4. Hành Động Tiếp Theo
+
+Khi chọn **[C]**: Tải `steps/step-02-readme.md`

package/bmm/workflows/document-odoo/steps/step-02-readme.md

@@ -0,0 +1,98 @@
+# Bước 2: Tạo README.rst (OCA Standard)
+
+## 1. Cấu Trúc README.rst Chuẩn OCA
+
+```rst
+====================
+{Module Display Name}
+====================
+
+.. 
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+   !! This file is generated by oca-gen-addon-readme !!
+   !! changes will be overwritten.                   !!
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
+    :target: https://odoo-community.org/page/development-status
+    :alt: Beta
+.. |badge2| image:: https://img.shields.io/badge/licence-LGPL--3-blue.png
+    :target: http://www.gnu.org/licenses/lgpl-3.0-standalone.html
+    :alt: License: LGPL-3
+
+|badge1| |badge2|
+
+{Mô tả ngắn gọn về module}
+
+**Table of contents**
+
+.. contents::
+   :local:
+
+Usage
+=====
+
+{Hướng dẫn sử dụng cơ bản}
+
+Configuration
+=============
+
+{Hướng dẫn cấu hình nếu cần}
+
+Known issues / Roadmap
+======================
+
+{Các vấn đề đã biết và kế hoạch phát triển}
+
+Bug Tracker
+===========
+
+Bugs are tracked on `GitHub Issues <https://github.com/OCA/{repo}/issues>`_.
+
+Credits
+=======
+
+Authors
+~~~~~~~
+
+* {Author Name}
+
+Maintainers
+~~~~~~~~~~~
+
+{Maintainer info}
+```
+
+## 2. Thu Thập Thông Tin README
+
+### 2.1 Mô Tả Module
+**Tiêu đề:** ___
+
+**Mô tả ngắn (1-2 câu):**
+> ___
+
+**Mô tả chi tiết:**
+> ___
+
+### 2.2 Tính Năng Chính
+1. ___
+2. ___
+3. ___
+
+### 2.3 Cấu Hình Cần Thiết
+- [ ] Không cần cấu hình đặc biệt
+- [ ] Cần cấu hình: ___
+
+---
+
+## 3. Menu
+
+```
+[C] Tiếp tục - Tạo User Guide
+[P] Preview - Xem trước README
+[B] Quay lại
+```
+
+## 4. Hành Động Tiếp Theo
+
+Khi chọn **[C]**: Tải `steps/step-03-user-guide.md`

package/bmm/workflows/document-odoo/steps/step-03-user-guide.md

@@ -0,0 +1,76 @@
+# Bước 3: Tạo User Guide
+
+## 1. Cấu Trúc User Guide
+
+### 1.1 Template User Guide
+
+```markdown
+# {Module Name} - Hướng Dẫn Sử Dụng
+
+## Giới Thiệu
+{Mô tả ngắn về module và mục đích}
+
+## Yêu Cầu
+- Odoo phiên bản: {version}
+- Modules phụ thuộc: {list}
+
+## Cài Đặt
+1. Copy module vào addons path
+2. Cập nhật Apps list
+3. Tìm và cài đặt module
+
+## Hướng Dẫn Sử Dụng
+
+### {Tính năng 1}
+**Mục đích:** {mô tả}
+
+**Các bước thực hiện:**
+1. Vào menu {menu path}
+2. Nhấn nút {button}
+3. Điền thông tin...
+
+![Screenshot](./static/description/screenshot1.png)
+
+### {Tính năng 2}
+...
+
+## Câu Hỏi Thường Gặp (FAQ)
+
+**Q: {Câu hỏi 1}?**
+A: {Trả lời}
+
+**Q: {Câu hỏi 2}?**
+A: {Trả lời}
+
+## Liên Hệ Hỗ Trợ
+{Thông tin liên hệ}
+```
+
+## 2. Thu Thập Nội Dung
+
+### 2.1 Các Tính Năng Cần Document
+
+| # | Tính năng | Menu Path | Screenshots |
+|---|-----------|-----------|-------------|
+| 1 | | | Có/Không |
+| 2 | | | |
+
+### 2.2 FAQ
+
+| Câu hỏi | Trả lời |
+|---------|---------|
+| | |
+
+---
+
+## 3. Menu
+
+```
+[C] Tiếp tục - Hoàn thành
+[A] API Docs - Thêm API documentation
+[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/document-odoo/steps/step-04-complete.md

@@ -0,0 +1,58 @@
+# Bước 4: Hoàn Thành Tài Liệu
+
+## 1. Tóm Tắt
+
+```
+📝 ODOO DOCUMENTATION COMPLETE
+
+Module: {module_name}
+
+FILES CREATED:
+├── README.rst ✓
+├── static/description/index.html ✓
+├── doc/user_guide.md ✓
+└── doc/changelog.md ✓
+
+SECTIONS:
+├── Introduction ✓
+├── Installation ✓
+├── Configuration ✓
+├── Usage ✓
+└── FAQ ✓
+```
+
+## 2. Checklist OCA Compliance
+
+- [ ] README.rst có đầy đủ sections
+- [ ] static/description có icon.png (128x128)
+- [ ] Badges hiển thị đúng
+- [ ] License declaration đầy đủ
+- [ ] Author information chính xác
+
+## 3. Đầu Ra
+
+### 3.1 Files Tạo/Cập Nhật
+
+```
+{module_path}/
+├── README.rst
+├── static/
+│   └── description/
+│       ├── icon.png
+│       └── index.html
+└── doc/
+    ├── user_guide.md
+    └── changelog.md
+```
+
+### 3.2 Doc Spec
+
+Lưu vào: `{planning_artifacts}/doc-{module_name}.md`
+
+## 4. Bước Tiếp Theo
+
+```
+[1] Tài liệu module khác
+[2] Tạo API documentation
+[X] Quay về menu chính
+```

package/bmm/workflows/document-odoo/workflow.md

@@ -0,0 +1,30 @@
+---
+name: document-odoo
+description: Tạo tài liệu cho Odoo modules - README, User Guide, API docs theo chuẩn OCA.
+web_bundle: true
+---
+
+# Quy Trình Tài Liệu Hóa Odoo Module
+
+**Mục tiêu:** Tạo tài liệu toàn diện cho Odoo modules theo tiêu chuẩn OCA, bao gồm README.rst, User Guide, và API documentation.
+
+**Vai trò:** Technical Writer chuyên về Odoo với kiến thức chuẩn OCA documentation.
+
+---
+
+## 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: {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/document-odoo/steps/step-01-init.md`