@relipa/ai-flow-kit 0.1.4-beta.0 → 0.1.5-beta.0

package/README.md

@@ -10,18 +10,21 @@ Developers only need a single command to load ticket context → AI automaticall
 
 | Problem | Solution |
 |--------|-----------|
-| Multi-step, complex installation | `aiflow init` — 1 command to set up everything |
-| Need long prompts for AI to understand | `aiflow use PROJ-33` — AI automatically reads from ticket |
+| Multi-step, complex installation | `ak init` — 1 command to set up everything |
+| Need long prompts for AI to understand | `ak use PROJ-33` — AI automatically reads from ticket |
 | Too many templates, not sure which to use | AI auto-detects task type and selects the appropriate skill |
 | New plugins (superpowers, MCP...) require manual setup | Package auto-sets up hooks, skills, and MCP on init |
 | Missing investigation / bug reproduction flow | Skill `investigate-bug` (inherits systematic-debugging) |
 | Missing impact analysis flow | Skill `impact-analysis` |
 | Hard to resume tasks | **State Resumption**: Unified `plan/` docs, `task-summary.md` progress tracking, and intelligent session continuity (automatic Gate 3 resumption). |
+| BA writing specs without a structured workflow | `ak use PROJ-33` (taskType: spec) → AI follows 4-gate BA workflow (Q&A → Prototype → UC Spec) |
+| QA creating test cases manually without structure | `ak use PROJ-33` (taskType: testcase) → AI follows 4-gate QA workflow (Analysis → Scenarios → Detailed TCs → Review) |
+| Gate transitions happen without formal approval | Gate review protocol — each gate requires explicit `APPROVED` before AI advances to the next gate |
 
 ## Documentation & Guides
 
 > [!TIP]
-> After running `aiflow init`, documentation files are automatically copied to `.aiflow/docs/` in your project for easy access.
+> After running `ak init`, documentation files are automatically copied to `.aiflow/docs/` in your project for easy access.
 
 - **[Quick Start Guide](https://github.com/example/ai-flow-kit/blob/main/docs/common/QUICK_START.md)** — Step-by-step instructions for developers.
 - **[Full Workflow (5 Gates)](https://github.com/example/ai-flow-kit/blob/main/docs/common/AIFLOW.md)** — In-depth look at the Gate process.
@@ -31,14 +34,14 @@ Developers only need a single command to load ticket context → AI automaticall
 
 ---
 
-## Overview Flow
+## Coding Flow
 
 ```
 PM writes ticket on Backlog/Jira
         │
         ▼
 ⛩️ GATE 1 — AI Analyze Requirement          [AI + DEV]
-  aiflow use PROJ-33   →   claude
+  ak use PROJ-33   →   claude
   AI loads ticket + reads source code
   AI asks clarifying questions (max 1 in Fast mode)
   AI outputs: plan/PROJ-33/requirement.md (Lite in Fast mode)
@@ -73,14 +76,15 @@ PM writes ticket on Backlog/Jira
 ## Execute Test Flow
 
 ```
-aiflow execute PROJ-44  (or ./testcases.md  or  aiflow execute)
+ak execute PROJ-44  (or ./testcases.md  or  ak execute)
         │
         ▼
 ⛩️ GATE 1 — Pre-flight & Work Plan           [AI + QA]
   Parse TC file → verify ak-test/{repo}/ exists
   Check BASE_URL env var + playwright.config.ts
   Create execution work plan
-        │ Ready
+  QA reviews → "APPROVED"
+        │ APPROVED
         ▼
 ⛩️ GATE 2 — Script Sync                      [AI]
   Hash-based TC↔script sync
@@ -88,69 +92,107 @@ aiflow execute PROJ-44  (or ./testcases.md  or  aiflow execute)
   Uses Playwright MCP for selectors — never fabricates
         │ Scripts synced
         ▼
-⛩️ GATE 3 — Execute & Evidence               [AI]
+⛩️ GATE 3 — Execute & Evidence               [AI + QA]
   Run: npx playwright test
   Organize evidence per run-{N}/: screenshots, trace.zip, result.md
   Auto-draft bug files for failed TCs
   Support RETEST: [TC_ID] loop
-        │ Tests done
+  QA reviews → "APPROVED"
+        │ APPROVED
         ▼
 ⛩️ GATE 4 — Report & Bug Logging             [AI + QA]
   Generate testreport.md with Go/No-Go recommendation
   Log each failed TC to Jira/Backlog — interactive confirm per bug
+  QA reviews → "APPROVED"
         │
         ▼
        DONE
 ```
 
+> **Entry points:** `ak execute PROJ-44` (from ticket) · `ak execute ./testcases/AD10.md` (from file) · `ak execute` (manual — AI asks for TC file path)
+
 ---
 
-## Execute Test Flow
+## Create Spec Flow
 
-Flow độc lập cho QA — không cần chạy lại phân tích (Gates 1–2 của Development Flow).
+```
+ak use PROJ-33  (taskType: spec)  →  claude
+        │
+        ▼
+⛩️ GATE 1 — Phân tích Yêu cầu Ban đầu        [AI + BA]
+  AI đọc ticket, phân tích yêu cầu, phân loại Facts vs Assumptions
+  AI phát hiện Gaps và tạo danh sách câu hỏi Q&A cần làm rõ
+  BA review Q&A → "APPROVED"
+        │ APPROVED
+        ▼
+⛩️ GATE 2 — Q&A Loop & Confirm               [AI + BA]
+  AI cập nhật phân tích theo từng câu trả lời của BA
+  AI re-check Q&A đến khi tất cả được xác nhận (Confirmed)
+  BA xác nhận toàn bộ Q&A → "APPROVED"
+        │ APPROVED
+        ▼
+⛩️ GATE 3 — Prototype Design                  [AI + BA]
+  AI tạo HTML/CSS prototype cho các màn hình chính
+  BA review UI flow → "APPROVED"
+        │ APPROVED
+        ▼
+⛩️ GATE 4 — UC Spec hoàn chỉnh               [AI + BA]
+  AI tạo đầy đủ UC Spec document (flows, business rules, validations)
+  BA review → "APPROVED"
+        │
+        ▼
+       DONE
+```
+
+> **Entry point:** `ak use PROJ-33` → chọn taskType **"spec"** trong danh sách — AI tự động khởi chạy BA workflow.
+
+---
+
+## Create Testcase Flow
 
 ```
-QA nhận TC file (từ ticket hoặc file)
+ak use PROJ-33  (taskType: testcase)  →  claude
         │
         ▼
-⛩️ GATE 1 — Context & Work Plan              [AI + QA]
-  aiflow execute PROJ-44   →   claude
-  AI kiểm tra: MCP Playwright, ak-test/, BASE_URL, playwright.config.ts
-  AI parse TC file → extract TCs, phân loại Auto / Manual
-  AI xuất work plan + danh sách TCs cần thực thi
-        │ Work Plan ready
+⛩️ GATE 1 — Phân tích Yêu cầu & Rủi ro      [AI + QA]
+  AI đọc ticket/spec, phân tích scope và rủi ro
+  AI đọc source code để tìm validation rules và business logic ẩn
+  AI đặt câu hỏi làm rõ yêu cầu
+  QA review → "APPROVED"
+        │ APPROVED
         ▼
-⛩️ GATE 2 — Script Sync                      [AI]
-  Hash-based TC ↔ script sync
-  Gen mới TC chưa có script (Playwright MCP → selector DOM thật)
-  Cập nhật script đã thay đổi, bỏ qua script không đổi
-  Không fabricate selector — luôn lấy từ DOM thật
-        │ Scripts synced
+⛩️ GATE 2 — Xây dựng Scenarios & Checklist   [AI + QA]
+  AI generate checklist theo nhóm (Functional, Non-functional, Data, Regression)
+  AI kiểm tra Dev Artifacts (PR diff) để bổ sung regression TCs
+  AI output: test-plan/checklist.md
+  QA review → "APPROVED"
+        │ APPROVED
         ▼
-⛩️ GATE 3 — Execute & Evidence               [AI]
-  Chạy Playwright, tổ chức evidence theo run-{N}/
-  Cập nhật cột R1/R2 trong TC file
-  Tổng hợp kết quả pass/fail per TC
-        │ Tests done
+⛩️ GATE 3 — Thiết kế Test Case chi tiết      [AI + QA]
+  AI tạo bảng test case đầy đủ (TC_ID, Steps, Expected Result)
+  AI áp dụng kỹ thuật: BVA, Equivalence Partitioning, Decision Table
+  AI output: test-plan/test-cases/
+  QA review → "APPROVED"
+        │ APPROVED
         ▼
-⛩️ GATE 4 — Report & Bug Logging             [AI + QA]
-  AI tạo: testreport.md
-  AI hỏi từng bug → QA xác nhận log lên Jira/Backlog
-  QA review → DONE
+⛩️ GATE 4 — Review & Tối ưu                  [AI + QA]
+  AI review coverage, loại bỏ duplicate, bổ sung edge cases còn thiếu
+  AI export final test case set: test-plan/test-cases/final-testcases.md
+  QA review → "APPROVED"
         │
         ▼
        DONE
 ```
 
-> **Entry points:** `aiflow execute PROJ-44` (từ ticket) · `aiflow execute ./testcases/AD10.md` (từ file) · `aiflow execute` (manual — AI hỏi TC file path)
+> **Entry point:** `ak use PROJ-33` → chọn taskType **"testcase"** trong danh sách — AI tự động khởi chạy QA workflow.
 
 ---
 
 ## Installation
 
 ```bash
-# Stable version
-npm install -g @relipa/ai-flow-kit
+# Stable version (latest)
+npm install -g @relipa/ai-flow-kit@latest
 
 # Beta version (recommend for newest features)
 npm install -g @relipa/ai-flow-kit@beta
@@ -165,32 +207,40 @@ npm uninstall -g @relipa/ai-flow-kit
 
 | Command | Description |
 |---------|-------------|
-| `aiflow init` | Setup framework, adapters, and multi-AI rules. |
-| `aiflow use <ticket...>` | Load context from one or more tickets/files. First target is primary; rest become supplementary. |
-| `aiflow execute <target>` | **QA:** Execute test cases — load TC file, sync Playwright scripts, run and collect evidence. |
-| `aiflow fetch-links <url>` | Fetch a Backlog/Jira link and print SupplementaryContext JSON (used by AI at runtime). |
-| `aiflow task` | Manage multiple tasks — pause, switch, resume. |
-| `aiflow task next` | Finalize gate approval and prepare for fresh session. |
-| `aiflow prompt` | Generate tool-optimized prompts (`--env cursor`). |
-| `aiflow sync-skills` | Manually synchronize AI Instruction files with local custom skills. |
-| `aiflow telemetry` | Manage telemetry tracking (enable/disable/status). |
-| `aiflow guide` | View integrated multi-AI integration guide. |
-
-### `aiflow init`
+| `ak init` | Setup framework, adapters, and multi-AI rules. |
+| `ak use <ticket...>` | Load context from one or more tickets/files. First target is primary; rest become supplementary. |
+| `ak execute <target>` | **QA:** Execute test cases — load TC file, sync Playwright scripts, run and collect evidence. |
+| `ak fetch-links <url>` | Fetch a Backlog/Jira link and print SupplementaryContext JSON (used by AI at runtime). |
+| `ak task` | Manage multiple tasks — pause, switch, resume. |
+| `ak task next` | Finalize gate approval and prepare for fresh session. |
+| `ak prompt` | Generate tool-optimized prompts (`--env cursor`). |
+| `ak sync-skills` | Manually synchronize AI Instruction files with local custom skills. |
+| `ak telemetry` | Manage telemetry tracking (enable/disable/status). |
+| `ak guide` | View integrated multi-AI integration guide. |
+| `ak doctor` | Check setup health and token savings status. |
+| `ak update` | Update skills, rules, and templates to the latest version. |
+| `ak remove` | Remove ai-flow-kit scaffolding from project. |
+| `ak detect "<description>"` | Auto-detect task type from a description string. |
+| `ak validate <file>` | Validate code output against team rules. |
+| `ak memory` | Save/search team knowledge base. |
+| `ak context` | Manage saved contexts (show/list/save/load/delete/clear). |
+| `ak gate <n> start\|approved` | Log gate transitions — called automatically by AI. |
+
+### `ak init`
 
 Initial setup for the project. Run once per project.
 
 ```bash
 # Single framework + adapter
-aiflow init --framework spring-boot --adapter backlog
+ak init --framework spring-boot --adapter backlog
 
 # Enable token savings tools
-aiflow init --with-rtk                     # RTK: compress bash outputs (60–90% reduction)
-# aiflow init --with-gitnexus               # GitNexus: code intelligence (waits for index)
-# aiflow init --with-gitnexus --no-wait     # GitNexus: index in background
+ak init --with-rtk                     # RTK: compress bash outputs (60–90% reduction)
+# ak init --with-gitnexus               # GitNexus: code intelligence (waits for index)
+# ak init --with-gitnexus --no-wait     # GitNexus: index in background
 
 # Multiple frameworks and adapters
-aiflow init --framework spring-boot,reactjs --adapter backlog,jira
+ak init --framework spring-boot,reactjs --adapter backlog,jira
 ```
 
 **What gets automatically set up:**
@@ -218,37 +268,37 @@ aiflow init --framework spring-boot,reactjs --adapter backlog,jira
 
 ---
 
-### `aiflow execute <target>`
+### `ak execute <target>`
 
 Execute test cases from a Backlog/Jira ticket, a TC file, or manually. The AI syncs Playwright scripts, runs them, collects evidence, and generates a test report.
 
 ```bash
 # From a ticket (taskType must be "execute")
-aiflow execute PROJ-44
+ak execute PROJ-44
 
 # From a TC file directly
-aiflow execute ./testcases/AD10.md
+ak execute ./testcases/AD10.md
 
 # Manual — AI asks for TC file path
-aiflow execute
+ak execute
 ```
 
 **What happens (4-gate Execute Flow):**
-1. **Gate 1 — Pre-flight:** Parse TC file, verify `ak-test/{repo}/` exists, check `BASE_URL` and `playwright.config.ts`
+1. **Gate 1 — Pre-flight:** Parse TC file, verify `ak-test/{repo}/` exists, check `BASE_URL` and `playwright.config.ts` — QA reviews → `APPROVED`
 2. **Gate 2 — Script Sync:** Hash-based TC↔script sync — gen new, update changed, skip unchanged (never fabricates selectors — uses Playwright MCP)
-3. **Gate 3 — Execute & Evidence:** Run Playwright, organize evidence per `run-{N}/`, update TC file R1/R2 columns
-4. **Gate 4 — Report & Bug Logging:** Generate `testreport.md`, ask per-bug Jira confirmation
+3. **Gate 3 — Execute & Evidence:** Run Playwright, organize evidence per `run-{N}/`, update TC file R1/R2 columns — QA reviews → `APPROVED`
+4. **Gate 4 — Report & Bug Logging:** Generate `testreport.md`, ask per-bug Jira confirmation — QA reviews → `APPROVED`
 
 > **Multi-AI:** Works with Claude, Gemini, Cursor, Copilot — the execute-flow skill is loaded via `ak init`/`ak up`.
 
 ---
 
-### `aiflow sync-skills`
+### `ak sync-skills`
 
 Synchronize AI instruction files (`CLAUDE.md`, `GEMINI.md`, etc.) and Skills without upgrading the package version. 
 
 ```bash
-aiflow sync-skills
+ak sync-skills
 ```
 
 **Features:**
@@ -258,59 +308,59 @@ aiflow sync-skills
 
 ---
 
-### `aiflow use <ticket...>`
+### `ak use <ticket...>`
 
 Load ticket context into `.aiflow/context/current.json`. Accepts **one or more targets** (ticket ID, Backlog/Jira URL, or local file). The first target becomes the **primary context**; any additional targets are appended as **`supplementaryContext[]`** for AI to read alongside the primary.
 
 ```bash
 # Single target (backward compatible)
-aiflow use PROJ-33
-aiflow use https://mycompany.backlog.com/view/PROJ-33
+ak use PROJ-33
+ak use https://mycompany.backlog.com/view/PROJ-33
 
 # Multiple targets — primary + supplementary
-aiflow use PROJ-33 PROJ-10 docs/arch.md
+ak use PROJ-33 PROJ-10 docs/arch.md
 # PROJ-33 drives Gate 1; PROJ-10 + docs/arch.md become supplementary context
 
 # Backlog / Jira ticket
-aiflow use PROJ-123
+ak use PROJ-123
 
 # Comments
-aiflow use PROJ-33 --with-comments
-aiflow use PROJ-33 --comments-last 5
-aiflow use PROJ-33 --comments-from 3
+ak use PROJ-33 --with-comments
+ak use PROJ-33 --comments-last 5
+ak use PROJ-33 --comments-from 3
 
 # Manual input
-aiflow use --manual
+ak use --manual
 
 # Load from local file (JSON or plain text)
-aiflow use --file task.md      # Auto-generates taskId from filename & prompts for taskType
+ak use --file task.md      # Auto-generates taskId from filename & prompts for taskType
 
 # Modes (Fast is default)
-aiflow use PROJ-33          # Fast Mode: skip Q&A, target < 5 min
-aiflow use PROJ-33 --full   # Full Mode: deep analysis with Q&A
+ak use PROJ-33          # Fast Mode: skip Q&A, target < 5 min
+ak use PROJ-33 --full   # Full Mode: deep analysis with Q&A
 
 # Save with custom name
-aiflow use PROJ-33 --save sprint-42-bug
+ak use PROJ-33 --save sprint-42-bug
 ```
 
 > **New in v0.1.0 — Auto Link Resolution:** When the primary ticket description contains Backlog/Jira URLs, `ak use` automatically fetches them and stores results in `supplementaryContext[]`. Comment links (`#comment-456` or `?focusedCommentId=456`) fetch **only that comment**. Capped at 5 auto-resolved links per `use` to keep loads fast.
 
 ---
 
-### `aiflow fetch-links <url>`
+### `ak fetch-links <url>`
 
 Fetch a single Backlog/Jira link and print a `SupplementaryContext` JSON object to stdout. Intended for AI runtime use inside the `read-study-requirement` skill when a link is found in the ticket description that wasn't already resolved at `use` time.
 
 ```bash
 # Backlog ticket → full ticket JSON
-aiflow fetch-links "https://company.backlog.com/view/PROJ-10"
+ak fetch-links "https://company.backlog.com/view/PROJ-10"
 
 # Backlog comment → that single comment only
-aiflow fetch-links "https://company.backlog.com/view/PROJ-10#comment-456"
+ak fetch-links "https://company.backlog.com/view/PROJ-10#comment-456"
 
 # Jira ticket / comment
-aiflow fetch-links "https://company.atlassian.net/browse/PROJ-10"
-aiflow fetch-links "https://company.atlassian.net/browse/PROJ-10?focusedCommentId=789"
+ak fetch-links "https://company.atlassian.net/browse/PROJ-10"
+ak fetch-links "https://company.atlassian.net/browse/PROJ-10?focusedCommentId=789"
 ```
 
 Output schema:
@@ -333,47 +383,47 @@ Exits non-zero with a stderr message if the URL is not a recognised Backlog/Jira
 
 ---
 
-### `aiflow task`
+### `ak task`
 
 Manage multiple tasks — pause a task, switch to another, and resume later while keeping full progress.
 
 ```bash
-aiflow task status                  # show active task and pending tasks
-aiflow task list                    # list all saved tasks
-aiflow task pause                   # pause current task (saves context + gate progress)
-aiflow task pause --note "waiting for API spec"   # pause with a note
-aiflow task switch PROJ-99          # pause current + switch to another task
-aiflow task resume PROJ-33          # resume a paused task (restores context + gate state)
-aiflow task reset  PROJ-33          # reset to Gate 1 (keeps ticket context, clears progress)
-aiflow task remove PROJ-33          # permanently delete all saved data for the task
-aiflow task next                    # approve current gate + prepare for fresh session
-aiflow task next --ticket PROJ-33   # same, but specify ticket explicitly
+ak task status                  # show active task and pending tasks
+ak task list                    # list all saved tasks
+ak task pause                   # pause current task (saves context + gate progress)
+ak task pause --note "waiting for API spec"   # pause with a note
+ak task switch PROJ-99          # pause current + switch to another task
+ak task resume PROJ-33          # resume a paused task (restores context + gate state)
+ak task reset  PROJ-33          # reset to Gate 1 (keeps ticket context, clears progress)
+ak task remove PROJ-33          # permanently delete all saved data for the task
+ak task next                    # approve current gate + prepare for fresh session
+ak task next --ticket PROJ-33   # same, but specify ticket explicitly
 ```
 
 **Use case — switching tasks mid-flow:**
 
 ```bash
 # Working on PROJ-33 at Gate 2...
-aiflow task pause               # pauses and saves PROJ-33 progress
+ak task pause               # pauses and saves PROJ-33 progress
 
-aiflow use PROJ-99              # loads urgent task (auto-pauses current)
-claude                          # AI starts Gate 1 for PROJ-99
+ak use PROJ-99              # loads urgent task (auto-pauses current)
+claude                      # AI starts Gate 1 for PROJ-99
 
 # Done with PROJ-99, resuming PROJ-33
-aiflow task resume PROJ-33      # restores context
-claude                          # AI resumes from Gate 2 automatically
+ak task resume PROJ-33      # restores context
+claude                      # AI resumes from Gate 2 automatically
 ```
 
 Task state (context + gate progress) is saved in `.aiflow/tasks/<taskId>/`.
 
 ---
 
-### `aiflow doctor`
+### `ak doctor`
 
 Check if the setup is complete.
 
 ```bash
-aiflow doctor
+ak doctor
 ```
 
 ```
@@ -387,34 +437,34 @@ aiflow doctor
 
 ---
 
-### `aiflow update`
+### `ak update`
 
 Update skills, rules, and templates to the latest version.
 
 ```bash
-aiflow update
+ak update
 ```
 
 ---
 
-### `aiflow validate <file>`
+### `ak validate <file>`
 
 Validate code output against team rules.
 
 ```bash
-aiflow validate src/Payment.java --ruleset strict
+ak validate src/Payment.java --ruleset strict
 ```
 
 ---
 
-### `aiflow memory`
+### `ak memory`
 
 Save/search team knowledge.
 
 ```bash
-aiflow memory save "payment-flow" "Payment flow description..."
-aiflow memory search "payment"
-aiflow memory list
+ak memory save "payment-flow" "Payment flow description..."
+ak memory search "payment"
+ak memory list
 ```
 
 ---
@@ -430,6 +480,10 @@ aiflow memory list
 | `generate-spec` | "new feature", "spec", "design" | Write technical specs, integrates `brainstorming` |
 | `report-customer` | "customer report", "incident" | Write incident reports for Customer Service |
 | `figma-to-component` | "figma", "design", "generate component" | Read Figma design → generate React/Next.js App Router/Vue/Angular component. [Workflow guide](docs/common/workflows/figma.md) |
+| `generate-testcase` | "create testcase", "test case", "QA checklist" | Generate detailed test cases from requirements (4-phase: Analysis → Checklist → TC Table → Review) |
+| `execute-flow` | "execute test", "run test", taskType: execute | 4-gate test execution orchestrator with Playwright MCP |
+| `create-spec` | taskType: spec | BA 4-gate UC Spec workflow (Q&A → Prototype → UC Spec) |
+| `create-testcase` | taskType: testcase | QA 4-gate testcase creation workflow (Analysis → Scenarios → TCs → Review) |
 
 ### Superpowers skills (upstream, inherited from obra/superpowers)
 
@@ -512,7 +566,7 @@ ai-flow-kit/
 
 **Custom skill:** create `custom/skills/<name>/SKILL.md`
 
-Then run `aiflow update` or `aiflow sync-skills` to apply.
+Then run `ak update` or `ak sync-skills` to apply.
 
 ---
 
@@ -521,8 +575,8 @@ Then run `aiflow update` or `aiflow sync-skills` to apply.
 | Environment | Experience | Notes |
 |-----------|------------|---------|
 | Claude Code CLI (`claude`) | ⭐⭐⭐⭐⭐ | Full auto — skills, hook, automatically loaded context |
-| Claude Extension (VS Code) | ⭐⭐⭐ | `aiflow prompt <type>` → copy paste |
-| Antigravity / Cursor | ⭐⭐⭐ | `aiflow prompt <type>` → copy paste |
+| Claude Extension (VS Code) | ⭐⭐⭐ | `ak prompt <type>` → copy paste |
+| Antigravity / Cursor | ⭐⭐⭐ | `ak prompt <type>` → copy paste |
 
 ---
 
@@ -530,8 +584,17 @@ Then run `aiflow update` or `aiflow sync-skills` to apply.
 
 > Summary of major changes per version. See full details in [CHANGELOG.md](docs/common/CHANGELOG.md).
 
+### v0.1.4 — 2026-06-29
+- **Create Spec Flow (4-Gate BA Workflow):** New `taskType: "spec"` — Q&A Analysis → Prototype Design → UC Spec. AI follows UCflow process guided by `ba-skills/` sub-skills.
+- **Create Testcase Flow (4-Gate QA Workflow):** New `taskType: "testcase"` — Requirement Analysis → Scenario Building → Detailed TC Design → Review & Optimize. AI applies BVA, Equivalence Partitioning, Decision Table techniques.
+- **BA Skills Library:** New `ba-skills/` skill set covering initial analysis, Q&A generation, business rules, UC spec writing, and Mermaid flow diagrams.
+- **Test Skills Library:** New `test-skills/` skill set with 20+ sub-skills covering UI testing, business testing, data testing, integration testing, and domain-specific (CMS, E-commerce) test patterns.
+- **Gate Review Protocol:** Explicit QA/BA `APPROVED` required at each gate before AI advances — eliminates silent gate skipping.
+- **`gate-review` skill:** New orchestration skill that enforces the gate review protocol across all workflow types (coding, execute, spec, testcase).
+- Documentation: README updated with Coding Flow, Create Spec Flow, Create Testcase Flow diagrams; `aiflow` CLI alias fully renamed to `ak` throughout.
+
 ### v0.1.3 — 2026-06-18
-- **Execute Test Flow (4-Gate):** New `aiflow execute` command + `execute-flow` skill — Pre-flight → Script Sync → Execute & Evidence → Report & Bug Logging.
+- **Execute Test Flow (4-Gate):** New `ak execute` command + `execute-flow` skill — Pre-flight → Script Sync → Execute & Evidence → Report & Bug Logging.
 - **`script-sync` skill:** Hash-based TC↔Playwright script sync — gen new, update changed, skip unchanged. Uses MCP browser tools for selectors, never fabricates.
 - **`ak execute` command** (`ak ex` alias): Standalone QA entry point — accepts ticket ID, TC file path, or interactive mode.
 - **▶️ Execute Test** added to `ak use` type selector; `taskType: "execute"` routes AI to execute-flow skill automatically.
@@ -544,7 +607,7 @@ Then run `aiflow update` or `aiflow sync-skills` to apply.
 - **Task type selector in `ak use`:** Interactive list after loading ticket — auto-detects and pre-selects task type.
 - **Critical fix — `update`/`init` not updating CLAUDE.md/GEMINI.md:** Fixed 3 compounding causes (`framework` singular vs. plural, missing `force: true`, per-file confirm dialogs).
 - **Backup before overwrite:** AI instruction files backed up to `.aiflow/bk/YYYY-MM-DD_HH-MM_<filename>` before any overwrite.
-- **`aiflow update` no longer wipes `.claude/`:** Now clears only `.claude/skills/`, preserving `settings.json` and hooks.
+- **`ak update` no longer wipes `.claude/`:** Now clears only `.claude/skills/`, preserving `settings.json` and hooks.
 
 ### v0.1.1 — 2026-06-08
 - **Ubuntu/Linux clipboard in `ak prompt`:** Auto-detects display server (Wayland/X11) and package manager — offers to install clipboard tool if missing.
@@ -553,20 +616,6 @@ Then run `aiflow update` or `aiflow sync-skills` to apply.
 - **`figma-to-component` CSS tooling detection:** Branches on Tailwind / CSS Modules / styled-components / vanilla CSS; maps Figma Styles/Variables to existing tokens.
 - **Critical fix — `figma-to-component` source/installed divergence:** Synced both copies to canonical version with correct tool names and 4-tier framework detection.
 
-### v0.1.3 — 2026-06-22
-
-**QA Automation Suite — End-to-end test execution với Playwright MCP**
-
-- New `aiflow execute` command with full 4-gate Execute Flow (pre-flight → script sync → run → report).
-- New skill suite for QA: `execute-flow`, `automation-testing`, `script-sync`, `generate-testcase`, `generate-test-report`, `log-bug`, `test-analysis`, `evidence-aggregation`, `retest-orchestration`, `coverage-check`.
-- Playwright harness template (`custom/harness/playwright/`) — pre-wired `playwright.config.ts`, `BasePage`, fixtures, và auth setup.
-- New `aiflow scaffold` command (`ak sc`) — tự động tạo cấu trúc `ak-test/{repo}/` từ template.
-- Hash-based TC↔script sync: chỉ gen/update script khi TC thay đổi, bỏ qua TC không đổi — không mất thời gian re-gen.
-- Selector lấy từ DOM thật qua Playwright MCP — không fabricate, không đoán.
-- ML framework support: `python-ml` template + 7 ML skills (`frame-ml-problem`, `explore-data`, `design-experiment`, `train-model`, `evaluate-model`, `improve-algorithm`, `deploy-model`).
-- New `pr-impact-analysis` skill — phân tích breaking changes của PR trước khi merge.
-- Deprecated `aiflow` CLI alias — dùng `ak` thay thế (warning hiện khi dùng `aiflow`).
-
 ### v0.1.0 — 2026-05-28
 - Multi-target `ak use` — load multiple tickets/files in a single call (primary + supplementary).
 - Auto link resolution — auto-fetch Backlog/Jira URLs found in the ticket description (capped at 5 links).
@@ -590,47 +639,47 @@ Then run `aiflow update` or `aiflow sync-skills` to apply.
 - v0.0.8-beta.1: Actually removed auto-commit + added PreToolUse hook blocking `git commit/add/push`.
 
 ### v0.0.7 — 2026-05-08
-- `aiflow use --file` auto-generates `taskId` from filename + interactive `taskType` prompt.
+- `ak use --file` auto-generates `taskId` from filename + interactive `taskType` prompt.
 - Auto-generates `task-summary.md` at each gate transition.
 - Added NestJS and PHP Plain framework support.
-- New `aiflow sync-skills` command.
+- New `ak sync-skills` command.
 - Marker-based update for `CLAUDE.md`, `GEMINI.md`, `.cursorrules`.
 - Auto-manages `.gitignore` for generated files.
 
 ### v0.0.6 — 2026-04-29
 - **Fast Mode** enabled by default (reduced Q&A, single-session implementation).
-- New `aiflow task` command group (status/list/pause/switch/resume).
+- New `ak task` command group (status/list/pause/switch/resume).
 - Integrated RTK token compression (60–90% savings).
 - `--file` loader supports plain-text input.
 
 ### v0.0.5 — 2026-04-23
 - Telemetry MVP — opt-in tracking, HMAC-SHA256 signed payload, no prompt content logged.
-- New `aiflow gate <n> <action>` command for AI to call automatically on gate transitions.
-- Safe overwrite flow in `aiflow init` (backs up existing files before overwrite).
+- New `ak gate <n> <action>` command for AI to call automatically on gate transitions.
+- Safe overwrite flow in `ak init` (backs up existing files before overwrite).
 
 ### v0.0.1 — 2026-04-13
-- Initial release: `aiflow` CLI, 5-Gate workflow, 7 custom skills, support for Claude Code / Gemini / Copilot.
+- Initial release: `ak` CLI, 5-Gate workflow, 7 custom skills, support for Claude Code / Gemini / Copilot.
 
 ---
 
 ## Troubleshooting
 
-**`aiflow` not found:**
+**`ak` not found:**
 ```bash
-npm install -g @relipa/ai-flow-kit
+npm install -g @relipa/ai-flow-kit@latest
 ```
 
 **Backlog load fails:**
 ```bash
-aiflow doctor
+ak doctor
 # Re-setup credentials
-aiflow init --adapter backlog
+ak init --adapter backlog
 ```
 
 **Skills not loading in Claude:**
 ```bash
 # Ensure init was run outside Claude terminal (session-start hook needs restart)
-aiflow doctor
+ak doctor
 ```
 
 See more: [docs/common/troubleshooting.md](./docs/common/troubleshooting.md)