@leejungkiin/awkit 1.0.9 → 1.1.1

package/workflows/git/smart-git-ops.md

@@ -1,10 +1,10 @@
 ---
-description: 🤖 Tự động hóa git workflow hoàn chỉnh (audit → commit → push)
+description: 🤖 Tự động hóa git workflow hoàn chỉnh (audit → commit → push → telegram report)
 ---
 
 # /smart-git-ops - Complete Git Automation
 
-**Tự động hóa toàn bộ:** Audit → Semantic Commit → Push
+**Tự động hóa toàn bộ:** Audit → Semantic Commit → Push → Telegram Report
 
 ---
 
@@ -20,7 +20,7 @@ echo "🔍 Running pre-commit audit..."
 
 ---
 
-## Phase 2: Status & Staging
+## Phase 2: Status & Smart Staging
 
 // turbo
 ```bash
@@ -78,6 +78,48 @@ git push origin HEAD
 
 ---
 
+## Phase 7: Telegram Report 📨
+
+**Mục đích:** Sau khi push thành công, tự động tóm tắt các thay đổi và gửi báo cáo vào Telegram group.
+
+**Logic:**
+1. Lấy thông tin commit vừa push:
+   ```bash
+   COMMIT_HASH=$(git log -1 --format='%h')
+   COMMIT_MSG=$(git log -1 --format='%s')
+   BRANCH=$(git branch --show-current)
+   AUTHOR=$(git log -1 --format='%an')
+   FILES_CHANGED=$(git diff --stat HEAD~1 HEAD | tail -1)
+   REPO_NAME=$(basename $(git rev-parse --show-toplevel))
+   ```
+
+2. Tạo message tóm tắt (Markdown):
+   ```
+   🚀 *Git Push Report*
+   
+   📦 *Repo:* `{REPO_NAME}`
+   🌿 *Branch:* `{BRANCH}`
+   🔖 *Commit:* `{COMMIT_HASH}`
+   👤 *Author:* {AUTHOR}
+   
+   📝 *Message:* {COMMIT_MSG}
+   📊 *Changes:* {FILES_CHANGED}
+   🕐 *Time:* {timestamp}
+   ```
+
+3. Gửi qua `awkit tg send`:
+   // turbo
+   ```bash
+   awkit tg send --parse-mode md "<generated-report>"
+   ```
+
+**Fallback:** Nếu `awkit tg send` fail (chưa config), hiển thị hướng dẫn:
+```
+⚠️ Telegram chưa được cấu hình. Chạy: awkit tg setup
+```
+
+---
+
 ## 🎛️ Configuration
 
 User có thể config trong `.gemini/config.json`:
@@ -86,7 +128,8 @@ User có thể config trong `.gemini/config.json`:
   "smart_git_ops": {
     "auto_approve_timeout": 5,
     "run_audit": true,
-    "run_tests_before_push": false
+    "run_tests_before_push": false,
+    "telegram_report": true
   }
 }
 ```
@@ -95,9 +138,9 @@ User có thể config trong `.gemini/config.json`:
 
 ## ⚠️ NEXT STEPS
 
-Sau khi push thành công:
+Sau khi push & report thành công:
 ```
 1️⃣ Xem commit log (`git log --oneline -3`)
-2️⃣ Đóng task Beads liên quan (`bd update <id> --status done`)
+2️⃣ Đóng task trong Symphony (`symphony_complete_task(task_id)`)
 3️⃣ Tiếp tục task tiếp theo (`/next`)
 ```

package/workflows/lifecycle/debug.md

@@ -2,7 +2,7 @@
 description: 🐞 Sửa lỗi & Debug (Dual-Mode v5.0)
 ---
 
-# WORKFLOW: /debug - The Sherlock Holmes (Dual-Mode + Beads)
+# WORKFLOW: /debug - The Sherlock Holmes (Dual-Mode + Symphony)
 
 > **Mode A (Expert):** `/debug --auto-fix` -> Tự động phân tích và sửa lỗi.
 > **Mode B (Guided):** `/debug` -> Hướng dẫn thu thập thông tin -> Phân tích -> Menu sửa.
@@ -27,8 +27,8 @@ description: 🐞 Sửa lỗi & Debug (Dual-Mode v5.0)
 3.  **Auto-Fix (Safe Only):**
     -   Lỗi *Safe-to-fix*: Missing import, typo, undefined check -> Sửa ngay.
     -   Lỗi *Logic*: Báo cáo và đề xuất (không tự ý sửa).
-4.  **Beads Sync:**
-    -   Nếu lỗi Critical và không thể auto-fix -> `bd create "Fix Critical Bug in Cart.tsx" --label bug`.
+4.  **Symphony Sync:**
+    -   Nếu lỗi Critical và không thể auto-fix -> `symphony_create_task(title="Fix Critical Bug in Cart.tsx")`.
 5.  **Report:** "✅ Fixed 1 issue. ⚠️ Created task #456 for manual review."
 
 ---
@@ -74,7 +74,7 @@ description: 🐞 Sửa lỗi & Debug (Dual-Mode v5.0)
 2.  **Fix Options:**
     ```markdown
     1️⃣ 🔧 Em sửa ngay (Auto-fix)
-    2️⃣ 📿 Tạo task Beads để sửa sau
+    2️⃣ 📿 Tạo task Symphony để sửa sau
     3️⃣ 📝 Hướng dẫn anh tự sửa
     4️⃣ 🔍 Điều tra sâu hơn
     ```
@@ -86,11 +86,11 @@ description: 🐞 Sửa lỗi & Debug (Dual-Mode v5.0)
 
 ---
 
-## 🧠 Brain & Beads Logic
+## 🧠 Brain & Symphony Logic
 
 ### 1. Bug Tracking
 -   Mọi lỗi được phát hiện -> Ghi vào `brain/bugs/[date]_[issue].md`.
--   Nếu lỗi Critical -> Auto-create Beads task với tag `bug` và `high-priority`.
+-   Nếu lỗi Critical -> Auto-create Symphony task với tag `bug` và `high-priority`.
 
 ### 2. Knowledge Base
 -   Lỗi đã fix -> Lưu vào `brain/solutions/` để tham khảo sau.
@@ -104,7 +104,7 @@ description: 🐞 Sửa lỗi & Debug (Dual-Mode v5.0)
 ## 🛡️ Resilience Patterns
 
 -   **False Fix Detection:** Sau khi sửa, tự động chạy test. Nếu fail -> Rollback ngay.
--   **Unknown Error:** Nếu không tìm ra nguyên nhân sau 3 lần -> Tạo task Beads "Investigate Unknown Error" và gợi ý user tìm expert.
+-   **Unknown Error:** Nếu không tìm ra nguyên nhân sau 3 lần -> Tạo task Symphony "Investigate Unknown Error" và gợi ý user tìm expert.
 
 ---
 

package/workflows/lifecycle/deploy.md

@@ -2,7 +2,7 @@
 description: 🚀 Deploy lên Production (Dual-Mode v5.0)
 ---
 
-# WORKFLOW: /deploy - The Release Manager (Dual-Mode + Beads)
+# WORKFLOW: /deploy - The Release Manager (Dual-Mode + Symphony)
 
 > **Mode A (Expert):** `/deploy --prod --force` -> Bỏ qua checks, deploy ngay.
 > **Mode B (Guided):** `/deploy` -> Pre-flight Checks -> Config -> Deploy -> Verify.
@@ -23,9 +23,9 @@ description: 🚀 Deploy lên Production (Dual-Mode v5.0)
 2.  **Execute:**
     -   Chạy build script (`npm run build`).
     -   Chạy deploy command (Vercel/Docker/AWS).
-3.  **Beads Sync:**
-    -   Tạo release tag trong Beads: `bd release create v1.0.0`.
-    -   Mark tất cả tasks `in_progress` -> `done` (Optional).
+3.  **Symphony Sync:**
+    -   Complete all in-progress tasks: `symphony_complete_task(task_id, summary)`.
+    -   Report deployment progress.
 4.  **Report:** "✅ Deployed to Production. URL: [Link]"
 
 ---
@@ -35,7 +35,7 @@ description: 🚀 Deploy lên Production (Dual-Mode v5.0)
 ### Phase 1: Pre-Audit & Health Check
 1.  **Blocker Check:**
     -   Check `session.json`: Có test nào đang `skipped` không?
-    -   Check `bd list`: Có task nào `critical` đang mở không?
+    -   Check Symphony: Có task nào `critical` đang mở không?
     -   *If Issue:* ❌ "Khoan! Còn 2 bugs nghiêm trọng chưa fix. Bạn chắc chắn muốn deploy?"
 
 2.  **Environment Check:**
@@ -56,9 +56,9 @@ description: 🚀 Deploy lên Production (Dual-Mode v5.0)
 1.  **Smoke Test:**
     -   AI tự truy cập URL vừa deploy.
     -   Check HTTP 200, check JS errors.
-2.  **Beads Release:**
+2.  **Symphony Release:**
     -   "Tạo Release Note từ các tasks đã làm?"
-    -   Action: `bd release create` kèm danh sách tasks.
+    -   Action: Complete all related tasks in Symphony.
 3.  **Action Menu:**
     ```markdown
     1️⃣ 📢 Thông báo team (Copy release note)
@@ -68,11 +68,11 @@ description: 🚀 Deploy lên Production (Dual-Mode v5.0)
 
 ---
 
-## 🧠 Brain & Beads Logic
+## 🧠 Brain & Symphony Logic
 
 ### 1. Release Tracking
 -   Mỗi lần deploy thành công -> Tạo bản ghi trong `brain/releases/`.
--   Nội dung: Version, Date, Commit Hash, Link tới Beads Release.
+-   Nội dung: Version, Date, Commit Hash.
 
 ### 2. Deployment Knowledge
 -   Lưu các preferences của user (vd: "Luôn dung Vercel", "Luôn skip test ở Staging").
@@ -91,5 +91,5 @@ description: 🚀 Deploy lên Production (Dual-Mode v5.0)
 ```
 1️⃣ Monitor logs (`/logs`)
 2️⃣ Rollback nhanh (`/rollback`)
-3️⃣ Đóng task trong Beads (`/done`)
+3️⃣ Đóng task trong Symphony (`/done`)
 ```

package/workflows/lifecycle/master-code-workflow.md

@@ -23,7 +23,7 @@ description: Quy trình thiết kế tính năng toàn diện từ kiến trúc
 │  └── Domain → Data → Presentation layers                   │
 │                          ↓                                  │
 │  Phase 3: FEATURE SPECS                       │
-│  └── requirements.md → design.md → bd tasks                │
+│  └── requirements.md → design.md → Symphony tasks                │
 │                          ↓                                  │
 │  Phase 4: UI/UX DESIGN                                     │
 │  └── Design analysis + Platform guidelines                 │
@@ -206,9 +206,9 @@ Use `/auto-implement [feature-name]` for spec-driven auto-coding.
 
 ### 5.3. Progress Tracking
 
-Update `bd` status as you complete each task:
+Update Symphony status as you complete each task:
 ```bash
-bd close [id]
+symphony_complete_task(task_id)
 ```
 
 ---

package/workflows/lifecycle/plan.md

@@ -2,7 +2,7 @@
 description: 📝 Thiết kế tính năng (Dual-Mode v5.0)
 ---
 
-# WORKFLOW: /plan - The Logic Architect v3 (Dual-Mode + Beads)
+# WORKFLOW: /plan - The Logic Architect v3 (Dual-Mode + Symphony)
 
 > **Mode A (Expert):** `/plan "Feature Name" --auto` -> Tạo plan chuẩn ngay lập tức.
 > **Mode B (Guided):** `/plan` -> Dẫn dắt từng bước Socratic.
@@ -20,8 +20,8 @@ description: 📝 Thiết kế tính năng (Dual-Mode v5.0)
 1.  **Analyze Intent:** Extract feature name from args.
 2.  **Generate Spec:** Create `docs/specs/ecommerce-cart_spec.md` with standard sections.
 3.  **Generate Phases:** Create `plans/[timestamp]-ecommerce-cart/` with 4-6 standard phases.
-4.  **Sync Beads:** Auto-create tasks in Beads for each phase.
-5.  **Report:** "✅ Plan created at `plans/...`. 6 tasks synced to Beads."
+4.  **Sync Symphony:** Auto-create tasks in Symphony for each phase.
+5.  **Report:** "✅ Plan created at `plans/...`. 6 tasks synced to Symphony."
 
 ---
 
@@ -31,7 +31,7 @@ description: 📝 Thiết kế tính năng (Dual-Mode v5.0)
 1.  **Understand Intent:** "Mô tả ý tưởng của bạn đi? (Nói tự nhiên thôi)"
 2.  **Socratic Questions:** (Based on previous Logic Architect v2 logic)
     -   Auth? Files? Notifications? Payment?
-    -   *New:* "Có cần tạo task trong Beads luôn không?"
+    -   *New:* "Có cần tạo task trong Symphony luôn không?"
 
 ### Phase 2: Architecture & Flow
 1.  **Visualize:** Vẽ sơ đồ Mermaid (Flowchart/Entity Relationship).
@@ -45,44 +45,42 @@ description: 📝 Thiết kế tính năng (Dual-Mode v5.0)
 
 ### Phase 3: Plan Generation
 1.  **Action:** Tạo folder structure và file markdown (như v2).
-2.  **Sync Beads:** (Nếu user đồng ý ở Phase 1)
-    -   `bd create -t epic` → Create root epic
-    -   Loop qua từng Phase → `bd create --parent <epic-id>`
-    -   Loop qua từng Step → `bd create --parent <phase-id> --acceptance "..."`
-    -   `bd dep add` cho inter-phase dependencies
+2.  **Sync Symphony:** (Nếu user đồng ý ở Phase 1)
+    -   `symphony_create_task(title="<Feature>", priority=1)` → Create root task
+    -   Loop qua từng Phase → `symphony_create_task(title="Phase X", ...)`
+    -   Loop qua từng Step → `symphony_create_task(title="<Step>", acceptance="...")`
 
 ### Phase 4: Handoff
-1.  **Report:** Hiển thị chi tiết Plan và Link Beads.
+1.  **Report:** Hiển thị chi tiết Plan và Link Symphony.
 2.  **Next Steps Menu:**
     ```markdown
     1️⃣ 🚀 Bắt đầu code ngay (`/code phase-01`)
     2️⃣ 👁️ Xem trước UI (`/visualize`)
-    3️⃣ 📿 Xem danh sách task (`/todo`)
+    3️⃣ 🎵 Xem danh sách task (`/todo`)
     4️⃣ 🔄 Chỉnh sửa lại plan
     ```
 
 ---
 
-## 🧠 Brain & Beads Integration Details
+## 🧠 Brain & Symphony Integration Details
 
-### 1. Auto-Sync Logic (Hierarchical — v6.5)
+### 1. Auto-Sync Logic
 Khi tạo plan, hệ thống sẽ:
-1.  `bd create "<Feature>" -t epic --json` → Create root epic
-2.  For each phase: `bd create "Phase X" --parent <epic-id> --json`
-3.  For each task: `bd create "Task" --parent <phase-id> --acceptance "..." --json`
-4.  `bd dep add <phase-N+1> <phase-N>` → Sequential phase dependencies
-5.  Ghi epic mapping → `brain/active_plans.json`
+1.  `symphony_create_task(title="<Feature>", priority=1)` → Create root task
+2.  For each phase: `symphony_create_task(title="Phase X", ...)`
+3.  For each task: `symphony_create_task(title="Task", acceptance="...")`
+4.  Ghi task mapping → `brain/active_plans.json`
 
 ### 2. Context Retention
--   Lưu `epic_id` + phase IDs vào `brain/active_plans.json`.
--   Khi User gõ `/next`, hệ thống dùng `bd ready --parent <epic-id>` để suggest task.
+-   Lưu task IDs vào `brain/active_plans.json`.
+-   Khi User gõ `/next`, hệ thống dùng `symphony_available_tasks(filter="ready")` để suggest task.
 
 ---
 
 ## 🛡️ Resilience Patterns
 
 -   **Duplicate Plan:** Nếu folder đã tồn tại -> Hỏi "Ghi đè (Overwrite) hay Tạo bản sao (Copy)?"
--   **Beads Error:** Nếu `bd` command lỗi -> Vẫn tạo file MD, báo warning "Task tracking disabled".
+-   **Symphony Error:** Nếu Symphony unavailable -> Vẫn tạo file MD, báo warning "Task tracking disabled".
 
 ---
 

package/workflows/quality/audit.md

@@ -185,7 +185,7 @@ fi
 ```markdown
 1️⃣ Xem chi tiết vấn đề (scroll up)
 2️⃣ Sửa ngay (`/code`)
-3️⃣ Tạo task để sửa sau (`bd create "Fix warnings"`)
+3️⃣ Tạo task để sửa sau (`symphony_create_task(title="Fix warnings")`)
 4️⃣ Bỏ qua và commit (KHÔNG khuyến khích)
 ```
 

package/workflows/quality/project-audit.md

@@ -57,5 +57,5 @@ Tổng hợp kết quả thành báo cáo Markdown:
 3.  **Tối ưu**: [Refactor code rác, UI chưa mượt].
 
 ### 🤖 Lệnh tiếp theo
-- `bd create "Fix logic ABC"`
+- `symphony_create_task(title="Fix logic ABC")`
 - `/create-feature "Tên tính năng còn thiếu"`

package/workflows/roles/vibe-coding-master-workflow.md

@@ -27,7 +27,7 @@ priority: "high"
 **Trigger**: Complex Logic / New Component.
 1.  **Plan**: Check `code-quality.md` & `project-identity`.
 2.  **Structure**: File organization & Data flow.
-3.  **Output**: `docs/specs/[feature]/design.md` & `bd create` tasks.
+3.  **Output**: `docs/specs/[feature]/design.md` & Symphony tasks.
 
 ### Phase 4: Building (The Developer Hat) 💻
 **Trigger**: Approved Plan.
@@ -44,7 +44,7 @@ priority: "high"
 ## 🚀 How to Use
 - **Auto-Switch**: As an AI, I will seamlessly switch personas.
 - **Explicit Call**: You can say "Put on your PM hat" or "QA this for me".
-- **Progress**: Use `bd list` to track which phase we are in.
+- **Progress**: Use `symphony_available_tasks()` to track which phase we are in.
 
 ## 🌟 The Vibe
 - Keep it **Fast**.

package/workflows/smart-git-ops.md

@@ -0,0 +1,146 @@
+---
+description: 🤖 Tự động hóa git workflow hoàn chỉnh (audit → commit → push → telegram report)
+---
+
+# /smart-git-ops - Complete Git Automation
+
+**Tự động hóa toàn bộ:** Audit → Semantic Commit → Push → Telegram Report
+
+---
+
+## Phase 1: Pre-Commit Audit
+
+// turbo
+```bash
+# Run audit to check for issues
+echo "🔍 Running pre-commit audit..."
+```
+
+**Note:** Nếu audit phát hiện 🔴 Critical issues → DỪNG workflow.
+
+---
+
+## Phase 2: Status & Smart Staging
+
+// turbo
+```bash
+git status
+git diff --stat
+
+# Auto-stage known safe paths
+git add src/ app/ lib/ docs/ tests/ *.swift *.kt *.ts *.tsx
+```
+
+---
+
+## Phase 3: Generate Semantic Commit
+
+**Logic:**
+1. Phân tích thay đổi từ `git diff --staged`
+2. Tự động tạo commit message theo format: `type(scope): subject`
+3. Hiển thị message → User xác nhận (timeout 5s = auto-approve)
+
+**Example Output:**
+```
+📝 Proposed commit message:
+   feat(social): add following list view with real-time sync
+
+   ✅ Accept (Enter) | ❌ Edit (E)
+```
+
+---
+
+## Phase 4: Commit
+
+// turbo
+```bash
+git commit -m "<generated-message>"
+```
+
+---
+
+## Phase 5: Pre-Push Verification (Optional)
+
+```bash
+# Optional: Run quick build/lint if configured
+# Skip for docs-only changes
+```
+
+---
+
+## Phase 6: Push
+
+// turbo
+```bash
+git pull --rebase origin HEAD 2>/dev/null || true
+git push origin HEAD
+```
+
+---
+
+## Phase 7: Telegram Report 📨
+
+**Mục đích:** Sau khi push thành công, tự động tóm tắt các thay đổi và gửi báo cáo vào Telegram group.
+
+**Logic:**
+1. Lấy thông tin commit vừa push:
+   ```bash
+   COMMIT_HASH=$(git log -1 --format='%h')
+   COMMIT_MSG=$(git log -1 --format='%s')
+   BRANCH=$(git branch --show-current)
+   AUTHOR=$(git log -1 --format='%an')
+   FILES_CHANGED=$(git diff --stat HEAD~1 HEAD | tail -1)
+   REPO_NAME=$(basename $(git rev-parse --show-toplevel))
+   ```
+
+2. Tạo message tóm tắt (Markdown):
+   ```
+   🚀 *Git Push Report*
+   
+   📦 *Repo:* `{REPO_NAME}`
+   🌿 *Branch:* `{BRANCH}`
+   🔖 *Commit:* `{COMMIT_HASH}`
+   👤 *Author:* {AUTHOR}
+   
+   📝 *Message:* {COMMIT_MSG}
+   📊 *Changes:* {FILES_CHANGED}
+   🕐 *Time:* {timestamp}
+   ```
+
+3. Gửi qua `awkit tg send`:
+   // turbo
+   ```bash
+   awkit tg send --parse-mode md "<generated-report>"
+   ```
+
+**Fallback:** Nếu `awkit tg send` fail (chưa config), hiển thị hướng dẫn:
+```
+⚠️ Telegram chưa được cấu hình. Chạy: awkit tg setup
+```
+
+---
+
+## 🎛️ Configuration
+
+User có thể config trong `.gemini/config.json`:
+```json
+{
+  "smart_git_ops": {
+    "auto_approve_timeout": 5,
+    "run_audit": true,
+    "run_tests_before_push": false,
+    "telegram_report": true
+  }
+}
+```
+
+---
+
+## ⚠️ NEXT STEPS
+
+Sau khi push & report thành công:
+```
+1️⃣ Xem commit log (`git log --oneline -3`)
+2️⃣ Đóng task trong Symphony (`symphony_complete_task(task_id)`)
+3️⃣ Tiếp tục task tiếp theo (`/next`)
+```

package/workflows/ui/app-screen-analyzer.md

@@ -10,7 +10,7 @@ description: 📱 Phân tích màn hình & tạo đặc tả UI
 1.  **Input Analysis**: Detect App Type & Context.
 2.  **Screen Discovery**: Core → Secondary → Common.
 3.  **Feature Grouping**: Organize screens into Features.
-4.  **Spec Gen**: Create `docs/specs/[feature]/{requirements,design}.md` and init tasks via **bd**.
+4.  **Spec Gen**: Create `docs/specs/[feature]/{requirements,design}.md` and init tasks via **Symphony**.
 5.  **Overview**: Create `docs/specs/_overview.md`.
 
 ---
@@ -101,10 +101,10 @@ enum ViewState { case idle, loading, loaded([Model]), error(Error) }
 [Entry] -> [Screen1] -> [Screen2]
 ```
 
-### 3.3. Task Initialization (bd)
+### 3.3. Task Initialization (Symphony)
 ```bash
-bd create "Implement [Feature] - A1: Models & Repos" --body "File: Domain & Data\nValidates: RQ-01"
-bd create "Implement [Feature] - B1: [Screen1]" --body "File: Presentation/[Feature]/"
+symphony_create_task(title= "Implement [Feature] - A1: Models & Repos" --body "File: Domain & Data\nValidates: RQ-01"
+symphony_create_task(title= "Implement [Feature] - B1: [Screen1]" --body "File: Presentation/[Feature]/"
 ```
 
 ---

package/workflows/ui/create-feature.md

@@ -109,14 +109,14 @@ Property 1: [Property description]
 **Validates: Requirements X.X, X.X**
 ```
 
-#### Task Creation (using bd)
-Instead of a `tasks.md` file, use `bd` to create tracking issues:
+#### Task Creation (using Symphony)
+Instead of a `tasks.md` file, use Symphony to create tracking tasks:
 
 ```bash
 # Initialize tasks for the feature
-bd create "Implement [Feature Name] - Phase A: Foundation" --body "Models, Repositories"
-bd create "Implement [Feature Name] - Phase B: UI" --body "Views, Components"
-bd create "Implement [Feature Name] - Phase C: Logic" --body "ViewModels, Services"
+symphony_create_task(title="Implement [Feature Name] - Phase A: Foundation", description="Models, Repositories")
+symphony_create_task(title="Implement [Feature Name] - Phase B: UI", description="Views, Components")
+symphony_create_task(title="Implement [Feature Name] - Phase C: Logic", description="ViewModels, Services")
 ```
 
 #### product.md Template (Steering - one-time)
@@ -212,7 +212,7 @@ When initiating specs, follow this process:
 
 ### 1.1. Check Spec
 Is there a spec file in `docs/specs/[current-feature]/`?
-- **YES**: **Strict Implementation** mode (follow spec exactly, track progress with `bd`)
+- **YES**: **Strict Implementation** mode (follow spec exactly, track progress with Symphony)
 - **NO**: **Agile Coding** mode (quick implementation, optionally create spec first)
 
 ### 1.2. Agile Coding Mode
@@ -277,7 +277,7 @@ Users often FORGET these. AI MUST ADD:
 
 ### 3.4. Task Sync
 If working in **Strict Implementation** mode:
-- Mark tasks as completed using `bd close [id]`
+- Mark tasks as completed using `symphony_complete_task(task_id)`
 - Update `design.md` if architecture changes
 - Keep specs as source of truth
 
@@ -304,7 +304,7 @@ If working in **Strict Implementation** mode:
 
 1. Report: "Completed [Task Name]."
 2. List: "Changed files: [List]"
-3. If using specs: Update `bd` status with `bd update [id]`
+3. If using specs: Update task status with `symphony_report_progress(task_id)`
 4. Suggest next steps:
    - "Use `/run` to test."
    - "Use `/test` to verify logic."

package/workflows/ui/create-spec-architect.md

@@ -123,7 +123,7 @@ enum ViewState {
 - **Animations:** [Duration, Easing]
 ```
 
-### 3.4. Task Generation (bd commands)
+### 3.4. Task Generation (Symphony)
  
 **Script:** `docs/specs/[feature]/init_tasks.sh`
  
@@ -131,23 +131,23 @@ enum ViewState {
 #!/bin/bash
  
 # Phase A: Foundation
-bd create "Implement [Feature] - A1: Models" --body "File: Domain/Models/[Feature].swift\nValidates: RQ-01"
-bd create "Implement [Feature] - A2: Repository" --body "File: Data/Repositories/[Feature]Repository.swift\nValidates: RQ-01, RQ-02"
+symphony_create_task(title= "Implement [Feature] - A1: Models" --body "File: Domain/Models/[Feature].swift\nValidates: RQ-01"
+symphony_create_task(title= "Implement [Feature] - A2: Repository" --body "File: Data/Repositories/[Feature]Repository.swift\nValidates: RQ-01, RQ-02"
  
 # Phase B: UI
-bd create "Implement [Feature] - B1: Main View" --body "File: Presentation/[Feature]/[Feature]View.swift\nValidates: RQ-01"
-bd create "Implement [Feature] - B2: Components" --body "File: Presentation/[Feature]/Components/\nValidates: RQ-01"
+symphony_create_task(title= "Implement [Feature] - B1: Main View" --body "File: Presentation/[Feature]/[Feature]View.swift\nValidates: RQ-01"
+symphony_create_task(title= "Implement [Feature] - B2: Components" --body "File: Presentation/[Feature]/Components/\nValidates: RQ-01"
  
 # Phase C: Logic
-bd create "Implement [Feature] - C1: ViewModel" --body "File: Presentation/[Feature]/[Feature]ViewModel.swift\nValidates: RQ-01, RQ-02"
+symphony_create_task(title= "Implement [Feature] - C1: ViewModel" --body "File: Presentation/[Feature]/[Feature]ViewModel.swift\nValidates: RQ-01, RQ-02"
  
 # Phase D: Polish
-bd create "Implement [Feature] - D1: Localization" --body "Type: i18n"
-bd create "Implement [Feature] - D2: Accessibility" --body "Type: a11y"
+symphony_create_task(title= "Implement [Feature] - D1: Localization" --body "Type: i18n"
+symphony_create_task(title= "Implement [Feature] - D2: Accessibility" --body "Type: a11y"
  
 # Phase E: Verify
-bd create "Implement [Feature] - E1: Unit Tests" --body "Type: test"
-bd create "Implement [Feature] - E2: Final Review" --body "Type: checkpoint"
+symphony_create_task(title= "Implement [Feature] - E1: Unit Tests" --body "Type: test"
+symphony_create_task(title= "Implement [Feature] - E2: Final Review" --body "Type: checkpoint"
 ```
 
 ---
@@ -160,7 +160,7 @@ Sau khi tạo xong, trình bày:
 📁 Created: docs/specs/[feature]/
 ├── requirements.md (X requirements, Y criteria)
 ├── design.md (Component hierarchy, Models, UI specs)
-└── init_tasks.sh (Script to create bd tasks)
+└── init_tasks.sh (Script to create Symphony tasks)
 
 Ready for implementation with /auto-implement
 ```