@relipa/ai-flow-kit 0.1.5-beta.1 → 0.1.5

package/custom/rules/project-conventions.md

@@ -5,26 +5,26 @@
 
 ---
 
-## DEV Workflow Output Paths (`04.Coding/`)
+## DEV Workflow Output Paths (`AK-Docs/04.Coding/`)
 
 Áp dụng cho taskType: `feature` · `bug-fix` · `refactor` · `investigation` · `documentation`.
 
 | Output | Path | Note |
 |--------|------|------|
-| Requirement doc | `04.Coding/01.Requirements/[functionId]/[ticketId].md` | Gate 1 output |
-| Implementation plan | `04.Coding/02.Plans/[functionId]/[ticketId].md` | Gate 2 output — **NOT** `docs/superpowers/plans/` |
-| TDD Notes (test list + notes) | `04.Coding/03.TDD-Notes/[functionId]/[ticketId].md` | Gate 3 output |
-| Self-review / Summary | `04.Coding/04.Reviews/[functionId]/[ticketId].md` | Gate 4 output |
-| PR description | `04.Coding/05.Pull-Requests/[functionId]/[ticketId].md` | Gate 5 output |
-| Tracker | `04.Coding/00.Overview/_Index.md` | Update mỗi gate: `F-ID \| Ticket \| Dev \| Gate \| PR` |
+| Requirement doc | `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md` | Gate 1 output |
+| Implementation plan | `AK-Docs/04.Coding/02.Plans/[functionId]/[ticketId].md` | Gate 2 output — **NOT** `docs/superpowers/plans/` |
+| TDD Notes (test list + notes) | `AK-Docs/04.Coding/03.TDD-Notes/[functionId]/[ticketId].md` | Gate 3 output |
+| Self-review / Summary | `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md` | Gate 4 output |
+| PR description | `AK-Docs/04.Coding/05.Pull-Requests/[functionId]/[ticketId].md` | Gate 5 output |
+| Tracker | `AK-Docs/04.Coding/00.Overview/_Index.md` | Update mỗi gate: `F-ID \| Ticket \| Dev \| Gate \| PR` |
 
 > **Override:** The `writing-plans` skill defaults to `docs/superpowers/plans/<filename>.md`.
-> In this project, **always save plans to `04.Coding/02.Plans/[functionId]/[ticketId].md` instead.**
+> In this project, **always save plans to `AK-Docs/04.Coding/02.Plans/[functionId]/[ticketId].md` instead.**
 
 ### functionId & ticketId
 
 - `[functionId]` là mã định danh chức năng **do dự án quy định** (ví dụ `F-001_User-Login`, `AD06`, `UC-LOGIN`) — không ép format.
-  - Được xác định BẮT BUỘC ở Gate 1 Pre-flight: từ `functionId`/`screenId` trong `.aiflow/context/current.json` → suy từ file UC Spec input (nội dung hoặc đường dẫn thư mục, ví dụ `02.BA-Specs/04.UC-Specs/[functionId]/`) rồi **hỏi DEV xác nhận** → cuối cùng mới hỏi DEV cung cấp trực tiếp.
+  - Được xác định BẮT BUỘC ở Gate 1 Pre-flight: từ `functionId`/`screenId` trong `.aiflow/context/current.json` → suy từ file UC Spec input (nội dung hoặc đường dẫn thư mục, ví dụ `AK-Docs/02.BA-Specs/04.UC-Specs/[functionId]/`) rồi **hỏi DEV xác nhận** → cuối cùng mới hỏi DEV cung cấp trực tiếp.
   - KHÔNG ĐƯỢC ghi output khi chưa có functionId.
 - `[ticketId]` lấy từ `taskId` trong `.aiflow/context/current.json` (ví dụ `TICKET-100`). Một feature có nhiều ticket → folder theo functionId, file theo ticketId.
 
@@ -39,7 +39,7 @@
 When `writing-plans` skill says to announce the saved path, use the **actual path**:
 
 ```
-Plan complete and saved to `04.Coding/02.Plans/[functionId]/[ticketId].md`. Two execution options: ...
+Plan complete and saved to `AK-Docs/04.Coding/02.Plans/[functionId]/[ticketId].md`. Two execution options: ...
 ```
 
 Do NOT copy the hardcoded path from the skill template (`docs/superpowers/plans/`).
@@ -53,8 +53,8 @@ Before saving any requirement, plan, TDD-notes, review, or PR file, verify:
 - [ ] `functionId` đã được xác định/xác nhận ở Gate 1 Pre-flight
 - [ ] `[ticketId]` is read from `.aiflow/context/current.json`
 - [ ] Output path follows the table above — NOT the skill's default path, NOT the legacy `plan/` folder
-- [ ] Directory `04.Coding/<section>/[functionId]/` exists or will be created
-- [ ] Tracker `04.Coding/00.Overview/_Index.md` được cập nhật sau khi gate hoàn thành
+- [ ] Directory `AK-Docs/04.Coding/<section>/[functionId]/` exists or will be created
+- [ ] Tracker `AK-Docs/04.Coding/00.Overview/_Index.md` được cập nhật sau khi gate hoàn thành
 - [ ] Announced path in the handoff message matches the actual saved path
 
 ---

package/custom/skills/gate-review/SKILL.md

@@ -55,7 +55,7 @@ When generating the output for a gate (e.g. `requirement.md` or `plan.md`), foll
 3. If the JSON file does not exist, initialize it by writing an empty array `[]` (or `{ "comments": [] }`) to it. This ensures that the CLI verification commands do not fail due to a missing file when there are no comments.
 
 ### Step 2: Write the gate output file
-Write the gate output file (e.g. `04.Coding/01.Requirements/[functionId]/[ticketId].md`, `04.Coding/02.Plans/[functionId]/[ticketId].md`, or `docs/ak-[project]/...`) as specified by the gate instructions.
+Write the gate output file (e.g. `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md`, `AK-Docs/04.Coding/02.Plans/[functionId]/[ticketId].md`, or `docs/ak-[project]/...`) as specified by the gate instructions.
 
 ### Step 3: Display gate pause message
 

package/custom/skills/generate-spec/SKILL.md

@@ -14,12 +14,12 @@ keywords: spec, plan, implementation, tdd, coding plan
 
 ## Conditions to Enter Gate 2
 
-- ✅ Gate 1 APPROVED — `04.Coding/01.Requirements/[functionId]/[ticketId].md` reviewed and approved by DEV
+- ✅ Gate 1 APPROVED — `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md` reviewed and approved by DEV
 - ✅ Requirement document includes: requirements, solution, impact analysis, estimate
 
 ## Fast Mode Output Rules (CRITICAL)
 
-When updating `04.Coding/04.Reviews/[functionId]/[ticketId].md` in **fast mode**:
+When updating `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md` in **fast mode**:
 - **Keep it extremely short.**
 - Add a bullet point indicating Gate 2 plan is ready.
 - **DO NOT copy the entire plan.md into summary.md.**
@@ -30,7 +30,7 @@ When updating `04.Coding/04.Reviews/[functionId]/[ticketId].md` in **fast mode**
 
 ### Step 1: Read Approved Requirement
 
-Read `04.Coding/01.Requirements/[functionId]/[ticketId].md` — use the chosen approach, file list, and testing plan as input.
+Read `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md` — use the chosen approach, file list, and testing plan as input.
 
 ### Step 2: Create Implementation Plan
 

package/custom/skills/read-study-requirement/SKILL.md

@@ -30,7 +30,7 @@ Check `mode` in `.aiflow/context/current.json` before starting:
 
 ## Fast Mode Output Rules (CRITICAL)
 
-When creating `04.Coding/04.Reviews/[functionId]/[ticketId].md` during Gate 1:
+When creating `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md` during Gate 1:
 - You must create the `summary.md` file after Gate 1 is APPROVED, to track session progress.
 - Keep `summary.md` concise. Only include short bullet points tracking Gates.
 - Do not write verbose implementation details in `summary.md` at Gate 1.
@@ -48,7 +48,7 @@ When creating `04.Coding/04.Reviews/[functionId]/[ticketId].md` during Gate 1:
 3. Q&A: Ask at most **ONE** question if there is a blocking ambiguity.
    If the ticket + source file names make intent clear → skip Q&A entirely.
    Wait for answer before writing the requirement doc.
-4. Output `04.Coding/01.Requirements/[functionId]/[ticketId].md` with **3 sections only**:
+4. Output `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md` with **3 sections only**:
 
 ```markdown
 # Requirement: [Ticket ID] — [Title]
@@ -154,7 +154,7 @@ After the developer confirms the design direction (Step 2), extend with:
 
 ### Step 4: Write Requirement Document
 
-Save to `04.Coding/01.Requirements/[functionId]/[ticketId].md`:
+Save to `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md`:
 
 ```markdown
 # Requirement: [Ticket ID] — [Title]
@@ -284,7 +284,7 @@ Save to `04.Coding/01.Requirements/[functionId]/[ticketId].md`:
 ⏸️  GATE 1: REQUIREMENT DOCUMENT READY
 
 Ticket: [ticket-id] — [title]
-File:   04.Coding/01.Requirements/[functionId]/[ticketId].md
+File:   AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md
 
 Summary:
   Type:     [feature / bug-fix / refactor]
@@ -332,5 +332,5 @@ Please review the requirement document.
 - ❌ **DO NOT** skip impact analysis and effort estimate
 - ✅ **MUST** run `git status` + `git pull --ff-only` (Pre-flight) before reading source code, when working tree is clean
 - ✅ **MUST** read source code before Q&A begins
-- ✅ **MUST** save `04.Coding/01.Requirements/[functionId]/[ticketId].md`
+- ✅ **MUST** save `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md`
 - ✅ **MUST** display Gate 1 prompt and wait for `APPROVED`

package/custom/skills/review-plan/SKILL.md

@@ -43,7 +43,7 @@ Assess impact by reasoning about the changed files only:
 
 ## Fast Mode Output Rules (CRITICAL)
 
-When creating `04.Coding/04.Reviews/[functionId]/[ticketId].md` in **fast mode**:
+When creating `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md` in **fast mode**:
 - **Do not write long explanations or descriptions.**
 - **List format only:** Bullet points with `[NEW]`, `[MODIFIED]`, `[DELETED]`.
 - **Purpose:** Next to each file, write exactly 1 sentence explaining the *purpose* (the "why"), not the implementation details.
@@ -79,7 +79,7 @@ Run in the following mandatory order:
 
 ### Step 2: Create Summary Report
 
-Create file `04.Coding/04.Reviews/[functionId]/[ticketId].md`:
+Create file `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md`:
 
 ```markdown
 # Summary: [Ticket ID] — [Title]
@@ -148,7 +148,7 @@ Create file `04.Coding/04.Reviews/[functionId]/[ticketId].md`:
 ⏸️  GATE 4: WAITING FOR DEV REVIEW
 
 I have completed implementation and self-review.
-Summary: 04.Coding/04.Reviews/[functionId]/[ticketId].md
+Summary: AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md
 
 **Self-review results:**
 - Tests: ✅ [N] passed / ❌ [N] failed  

package/custom/templates/shared/gate-workflow.md

@@ -32,7 +32,7 @@ If `taskType` is missing or unrecognized, default to the DEV workflow and ask ON
 ### Cấu trúc thư mục đầu ra
 
 ```
-04.Coding/
+AK-Docs/04.Coding/
 ├── 00.Overview/_Index.md                          ← Tracker: F-ID | Ticket | Dev | Gate | PR (cập nhật mỗi gate)
 ├── 01.Requirements/[functionId]/[ticketId].md    ← Gate 1 tạo
 ├── 02.Plans/[functionId]/[ticketId].md           ← Gate 2 tạo
@@ -54,7 +54,7 @@ AI actively reads ticket + source code to understand the requirement:
 
    Kiểm tra theo thứ tự ưu tiên:
    1. Trường `functionId` hoặc `screenId` trong `.aiflow/context/current.json`
-   2. **Suy ra từ input**: nếu đầu vào có file UC Spec / tài liệu do BA bàn giao (trong `supplementaryContext[]`, description, hoặc file được chỉ định khi `ak use <file>`) → đọc nội dung file để tìm functionId, hoặc suy từ đường dẫn thư mục chứa file (ví dụ file nằm ở `02.BA-Specs/04.UC-Specs/[functionId]/UC-Spec_v1.md` → lấy `[functionId]`). Có thể tra thêm `04.Coding/00.Overview/_Index.md` hoặc `00.Project-Overview/Function-List.md` theo tên feature.
+   2. **Suy ra từ input**: nếu đầu vào có file UC Spec / tài liệu do BA bàn giao (trong `supplementaryContext[]`, description, hoặc file được chỉ định khi `ak use <file>`) → đọc nội dung file để tìm functionId, hoặc suy từ đường dẫn thư mục chứa file (ví dụ file nằm ở `AK-Docs/02.BA-Specs/04.UC-Specs/[functionId]/UC-Spec_v1.md` → lấy `[functionId]`). Có thể tra thêm `AK-Docs/04.Coding/00.Overview/_Index.md` hoặc `AK-Docs/00.Project-Overview/Function-List.md` theo tên feature.
       → Tìm được ứng viên → **hỏi xác nhận** thay vì hỏi trống:
       ```
       functionId của task này có phải là [X] không? (Y / hoặc nhập giá trị đúng)
@@ -67,9 +67,9 @@ AI actively reads ticket + source code to understand the requirement:
 
    → Đợi DEV trả lời, dùng giá trị này cho toàn bộ 5 Gates. **KHÔNG ĐƯỢC TIẾP TỤC NẾU CHƯA CÓ functionId.**
 
-   Sau đó kiểm tra thư mục `04.Coding/` trong root dự án — chưa có thì tạo đủ cây thư mục (00.Overview → 05.Pull-Requests) và file tracker `00.Overview/_Index.md`. Thông báo:
+   Sau đó kiểm tra thư mục `AK-Docs/04.Coding/` trong root dự án — chưa có thì tạo đủ cây thư mục (00.Overview → 05.Pull-Requests) và file tracker `00.Overview/_Index.md`. Thông báo:
    ```
-   ✓ Thư mục đầu ra: 04.Coding/
+   ✓ Thư mục đầu ra: AK-Docs/04.Coding/
    ✓ functionId: [functionId]  ✓ ticketId: [ticketId]
    → Bắt đầu Gate 1...
    ```
@@ -78,11 +78,11 @@ AI actively reads ticket + source code to understand the requirement:
 2. **Pre-flight: sync with remote** — run `git status --porcelain`; if working tree is clean, run `git pull --ff-only` to pull the latest source from remote. Skip the pull (with a `⚠️` notice to DEV) if there are uncommitted changes, the branch has diverged, or no remote tracking branch exists.
 3. Read source code — architecture, related files, data flow
 4. If anything is unclear — ask ONE question at a time, wait for reply
-5. Output `04.Coding/01.Requirements/[functionId]/[ticketId].md` with:
+5. Output `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md` with:
    - Requirements summary (ticket summary + AC), source code analysis
    - Proposed solution and approach
    - Impact analysis, effort estimate, testing plan
-6. Update tracker row in `04.Coding/00.Overview/_Index.md`: `| [F-ID] | [ticketId] | [feature] | [dev] | ✅⬜⬜⬜⬜ Gate 1 | - |`
+6. Update tracker row in `AK-Docs/04.Coding/00.Overview/_Index.md`: `| [F-ID] | [ticketId] | [feature] | [dev] | ✅⬜⬜⬜⬜ Gate 1 | - |`
 7. **INVOKE** `gate-review` skill (generate mode) — write `.aiflow/review/gate-1-[ticket-id].md`
 8. Display gate pause message from `gate-review` skill — wait for **APPROVED**
 
@@ -104,9 +104,9 @@ DO NOT just check format — **understand the content and propose solutions**.
 
 **INVOKE:** `generate-spec` skill, then `superpowers:writing-plans`
 
-- Create a detailed TDD implementation plan based on the approved requirement (`04.Coding/01.Requirements/[functionId]/[ticketId].md`).
-- Output `04.Coding/02.Plans/[functionId]/[ticketId].md` with the detailed TDD implementation plan (step-by-step, file list, test-first order).
-- Update tracker row in `04.Coding/00.Overview/_Index.md` (Gate 2 ✅).
+- Create a detailed TDD implementation plan based on the approved requirement (`AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md`).
+- Output `AK-Docs/04.Coding/02.Plans/[functionId]/[ticketId].md` with the detailed TDD implementation plan (step-by-step, file list, test-first order).
+- Update tracker row in `AK-Docs/04.Coding/00.Overview/_Index.md` (Gate 2 ✅).
 - **INVOKE** `gate-review` skill (generate mode) — write `.aiflow/review/gate-2-[ticket-id].md`
 - Display gate pause message from `gate-review` skill — CODE WILL NOT BE GENERATED until all items checked and APPROVED received.
 
@@ -128,10 +128,10 @@ Only runs after Gate 2 has been APPROVED.
 - Complex feature (3+ files): `superpowers:subagent-driven-development`
 - Write tests FIRST — run to confirm FAIL -> implement -> PASS.
 - Bug fix EXTRA: `superpowers:systematic-debugging` + `investigate-bug` skill first.
-- Output `04.Coding/03.TDD-Notes/[functionId]/[ticketId].md`:
+- Output `AK-Docs/04.Coding/03.TDD-Notes/[functionId]/[ticketId].md`:
   - **Test List** — danh sách test viết TRƯỚC khi implement (checklist `- [ ] TC-01: ...`)
   - **Implementation Notes** — ghi chú phát sinh trong quá trình code
-- Update tracker row in `04.Coding/00.Overview/_Index.md` (Gate 3 ✅) when tests PASS.
+- Update tracker row in `AK-Docs/04.Coding/00.Overview/_Index.md` (Gate 3 ✅) when tests PASS.
 
 > **Telemetry:** Run `ak gate 3 start --ticket [ticket-id]` when starting this gate. Run as-is — do NOT append shell redirects.
 
@@ -145,8 +145,8 @@ Mandatory order:
 1. `superpowers:verification-before-completion` — all tests must PASS
 2. `impact-analysis` skill — check for breaking changes
 3. Tick `custom/rules/review-checklist.md`
-4. Create `04.Coding/04.Reviews/[functionId]/[ticketId].md` — Test Results, Impact Analysis (files changed, affected features, breaking changes), Review Checklist
-5. Update tracker row in `04.Coding/00.Overview/_Index.md` (Gate 4 ✅)
+4. Create `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md` — Test Results, Impact Analysis (files changed, affected features, breaking changes), Review Checklist
+5. Update tracker row in `AK-Docs/04.Coding/00.Overview/_Index.md` (Gate 4 ✅)
 
 Then:
 - **INVOKE** `gate-review` skill (generate mode) — write `.aiflow/review/gate-4-[ticket-id].md`
@@ -172,12 +172,12 @@ Only runs after Gate 4 has been APPROVED.
 
 **INVOKE:** `superpowers:requesting-code-review`
 
-1. Create `04.Coding/05.Pull-Requests/[functionId]/[ticketId].md` — PR description gồm:
+1. Create `AK-Docs/04.Coding/05.Pull-Requests/[functionId]/[ticketId].md` — PR description gồm:
    - Ticket link, danh sách thay đổi chính, How to Test, Checklist for Reviewer
-   - **Related Docs links:** UC Spec (`02.BA-Specs/04.UC-Specs/[functionId]/`), Test Case (`03.Testing/01.Testcases/[functionId]/`), Dev Plan (`04.Coding/02.Plans/[functionId]/[ticketId].md`)
-2. **Lưu tài liệu `04.Coding/` lên remote (GitLab) TRƯỚC khi tạo Pull Request.**
+   - **Related Docs links:** UC Spec (`AK-Docs/02.BA-Specs/04.UC-Specs/[functionId]/`), Test Case (`AK-Docs/03.Testing/01.Testcases/[functionId]/`), Dev Plan (`AK-Docs/04.Coding/02.Plans/[functionId]/[ticketId].md`)
+2. **Lưu tài liệu `AK-Docs/04.Coding/` lên remote (GitLab) TRƯỚC khi tạo Pull Request.**
 3. Guide on creating a Pull Request — dùng nội dung file trên làm PR description.
-4. Update tracker row in `04.Coding/00.Overview/_Index.md` (Gate 5 ✅ Done + PR link).
+4. Update tracker row in `AK-Docs/04.Coding/00.Overview/_Index.md` (Gate 5 ✅ Done + PR link).
 
 > **Telemetry:** Run `ak gate 5 start --ticket [ticket-id]` when starting this gate. Run as-is — do NOT append shell redirects.
 

package/custom/templates/tools/claude.md

@@ -2,7 +2,7 @@
 
 You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
 
-> **Important:** Always read `.aiflow/context/current.json` to load ticket context and check the `04.Coding/` docs directory for existing progress before starting any task.
+> **Important:** Always read `.aiflow/context/current.json` to load ticket context and check the `AK-Docs/04.Coding/` docs directory for existing progress before starting any task.
 
 If Gate 1 does not auto-start, wait for the developer to type **"start"**, **"Gate 1"** or **"Analyze ticket"**.
 

package/custom/templates/tools/copilot.md

@@ -2,7 +2,7 @@
 
 You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
 
-> **Important:** Always check for context in `.aiflow/context/current.json` and progress in the `04.Coding/` docs folder before suggesting changes.
+> **Important:** Always check for context in `.aiflow/context/current.json` and progress in the `AK-Docs/04.Coding/` docs folder before suggesting changes.
 
 If the Gate Workflow hasn't started, wait for the developer to type **"start"** or **"Gate 1"**.
 

package/custom/templates/tools/cursor.md

@@ -2,7 +2,7 @@
 
 You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
 
-> **Important:** Always check `.aiflow/context/current.json` and the `04.Coding/` docs directory before starting any task to understand current context and progress.
+> **Important:** Always check `.aiflow/context/current.json` and the `AK-Docs/04.Coding/` docs directory before starting any task to understand current context and progress.
 
 If Gate 1 doesn't auto-start, wait for the developer to type **"start"**, **"Gate 1"** or **"Analyze ticket"**.
 

package/custom/templates/tools/gemini.md

@@ -2,7 +2,7 @@
 
 You are an expert AI assistant specialized in this project's stack. Follow the Gate Workflow and Team Rules strictly.
 
-> **Important:** When starting a session, always read `.aiflow/context/current.json` to load ticket context and check the `04.Coding/` docs directory for existing progress.
+> **Important:** When starting a session, always read `.aiflow/context/current.json` to load ticket context and check the `AK-Docs/04.Coding/` docs directory for existing progress.
 
 If no instructions are automatically followed, wait for the developer to type **"start"** or **"Gate 1"** to start the analysis.
 

package/custom/templates/tools/generic.md

@@ -4,7 +4,7 @@ You are an expert AI assistant. Follow the project's Gate Workflow and Team Rule
 
 ## Context Awareness
 - **Ticket context**: `.aiflow/context/current.json`
-- **Task progress**: `04.Coding/<section>/[functionId]/[ticketId].md`
+- **Task progress**: `AK-Docs/04.Coding/<section>/[functionId]/[ticketId].md`
 - **Rules**: `.rules/`
 
 Follow the gated workflow and rules defined below.

package/docs/common/AIFLOW.md

@@ -112,7 +112,7 @@ claude                           # open Claude → AI auto-starts Gate 1
 | 2 | Read `CLAUDE.md` + source code | Understand architecture, tech stack, patterns |
 | 3 | Investigate related files & data flow | Identify affected areas, dependencies |
 | 4 | Ask clarifying questions (one at a time) | Ensure full understanding |
-| 5 | Write `04.Coding/01.Requirements/[functionId]/[ticketId].md` | Structured requirement document |
+| 5 | Write `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md` | Structured requirement document |
 
 **AI asks questions when:**
 - Business requirements are vague or ambiguous
@@ -121,7 +121,7 @@ claude                           # open Claude → AI auto-starts Gate 1
 - Multiple approaches are possible and need input
 - Impact on existing features is unclear
 
-**Requirement Document Output (`04.Coding/01.Requirements/[functionId]/[ticketId].md`):**
+**Requirement Document Output (`AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md`):**
 
 ```
 ├── 1. Requirements Summary
@@ -166,13 +166,13 @@ Summary:
 - Approach: [brief description]
 - Files affected: [N] files
 
-→ Review: 04.Coding/01.Requirements/[functionId]/[ticketId].md
+→ Review: AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md
 → Type APPROVED to proceed
 → Or provide feedback to update
 ```
 
 **Gate 1 Output:**
-- `04.Coding/01.Requirements/[functionId]/[ticketId].md` approved by DEV
+- `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md` approved by DEV
 - DEV has typed "APPROVED"
 
 ---
@@ -265,14 +265,14 @@ In fast mode, AI uses the `tdd-lean` skill instead of per-test TDD to save massi
 | 1 | `superpowers:verification-before-completion` | All tests PASS |
 | 2 | `impact-analysis` skill | No breaking changes outside scope |
 | 3 | `custom/rules/review-checklist.md` | All items ticked |
-| 4 | Create `04.Coding/04.Reviews/[functionId]/[ticketId].md` | File exists and is complete |
+| 4 | Create `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md` | File exists and is complete |
 
 **If any step fails → AI fixes it first, without showing DEV.**
 
 **Summary report output:**
 
 ```
-04.Coding/04.Reviews/[functionId]/[ticketId].md
+AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md
 ├── List of changed files + reasons
 ├── Acceptance Criteria → results (Done/Not Done)
 ├── Tests: quantity, coverage
@@ -287,7 +287,7 @@ In fast mode, AI uses the `tdd-lean` skill instead of per-test TDD to save massi
 Tests: ✅ [N] passed
 Impact: [Low/Medium/High]
 Checklist: [N/N] ✅
-Summary: 04.Coding/04.Reviews/[functionId]/[ticketId].md
+Summary: AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md
 
 Type APPROVED if OK
 Type BUG: [description] if there are issues
@@ -299,7 +299,7 @@ Type BUG: [description] if there are issues
 - `BUG: requirement bug` → AI updates requirement doc → back to Gate 1
 
 **Gate 4 Output:**
-- `04.Coding/04.Reviews/[functionId]/[ticketId].md` completed
+- `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md` completed
 - DEV has typed "APPROVED"
 
 ---
@@ -458,7 +458,7 @@ aiflow telemetry disable              # disable tracking
 
 ## Multi-AI Environment Setup
 
-One of the core strengths of `ai-flow-kit` is that the **Gate Workflow** is tool-agnostic. Since state is saved in `.aiflow/context/current.json` and the `04.Coding/` docs directory, you can switch tools mid-task.
+One of the core strengths of `ai-flow-kit` is that the **Gate Workflow** is tool-agnostic. Since state is saved in `.aiflow/context/current.json` and the `AK-Docs/04.Coding/` docs directory, you can switch tools mid-task.
 
 ### How to Switch Tools
 1. **Analyze (Gate 1)** using Claude Code CLI (great for deep codebase scans).
@@ -506,7 +506,7 @@ A: Yes. Use `aiflow task pause` to save your current progress, then `aiflow use
 **Q: If I resume a task, will Claude know which gate to start at?**
 A: Yes. The SessionStart hook reads `.aiflow/tasks/<taskId>/task-state.json` and injects gate-aware instructions. If Gate 1 was already approved, Claude will skip to Gate 2, and so on.
 **Q: Can I resume a Gate 3 (Code Generation) task in a new chatbox?**
-A: Yes. Gate 3 progress is saved via `[x]` checkboxes in `04.Coding/02.Plans/[functionId]/[ticketId].md`. If you open a new chatbox and say "continue", the AI will automatically skip completed tasks and pick up exactly where it left off.
+A: Yes. Gate 3 progress is saved via `[x]` checkboxes in `AK-Docs/04.Coding/02.Plans/[functionId]/[ticketId].md`. If you open a new chatbox and say "continue", the AI will automatically skip completed tasks and pick up exactly where it left off.
 
 **Q: How does AI estimate effort?**
 A: AI analyzes the scope of changes (files affected, complexity, test requirements) and categorizes: S (< 1h), M (1-4h), L (4-8h), XL (8h+, should split).

package/docs/common/CHANGELOG.md

@@ -7,6 +7,17 @@ Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ---
 
+## [Unreleased]
+
+### Fixed
+
+- **`aiflow prompt <type>` still emitted `plan/[ticket-id]/...` paths** — The 0.1.5 migration to `04.Coding/` (see below) updated `gate-workflow.md`, the skills, all 5 tool templates, and `session-start.js`, but missed `scripts/prompt.js`. Its `PROMPT_TEMPLATES` (used by `aiflow prompt feature|bug-fix|refactor|investigation|impact-analysis|testing|documentation` to build the copy-paste prompt for Cursor/Gemini/manual use) still hard-coded `Output plan/[ticket-id]/requirement.md` / `plan.md` / `summary.md`, contradicting the `custom/rules/project-conventions.md` override appended later in the same prompt — this was the root cause of `/plan` still appearing at the project root even on 0.1.5-beta.1. All 11 occurrences now point at the current `04.Coding/<section>/[functionId]/[ticketId].md` convention.
+- **`ak init` still gitignored `plan/`** — `ensureAiflowGitignored()` in `scripts/init.js` added `plan/` to `.gitignore` on every init, reinforcing the deprecated convention. Removed; `04.Coding/` output now lives in `AK-Docs/` (see below) and isn't part of the source repo's `.gitignore` concerns.
+
+### Changed
+
+- **DEV workflow output relocated to `AK-Docs/04.Coding/`** — Per `docs/internal/Project-Structure.md` / `Coding-Structure.md`, `04.Coding/` (and its BA/QA siblings `02.BA-Specs/`, `03.Testing/`, `00.Project-Overview/`) belong under the `AK-Docs/` docs repo (a sibling of the source repo, synced via `scripts/docs-repo.js`), not directly at the source repo root. Updated all references across `CLAUDE.md`, `custom/rules/project-conventions.md`, `custom/templates/shared/gate-workflow.md`, the 5 tool templates, the DEV skills (`read-study-requirement`, `generate-spec`, `review-plan`, `gate-review`), `docs/common/AIFLOW.md` / `ai-integration.md` / `workflows/{bug-fix,feature}.md`, `scripts/hooks/session-start.js`, and `scripts/prompt.js`. `scripts/task.js` now resolves the coding dir via `resolveDocsRepoPath(PROJECT_DIR, 'AK-Docs')` (from `docs-repo.js`) instead of hard-coding the path, so `findTaskDocs()` / `detectCurrentGate()` look under `AK-Docs/04.Coding/` first, with the legacy `plan/<taskId>/` folder (at the source repo root) still checked as a fallback.
+
 ## [0.1.5] - 2026-07-01
 
 ### Added

package/docs/common/ai-integration.md

@@ -20,7 +20,7 @@
 When you run `aiflow init`, it generates a `.cursorrules` file. 
 - Cursor will automatically read this file to understand the **Gate Workflow**.
 - Use `@Codebase` when you need the AI to search across your whole project.
-- **Resumption**: If you start a task in Claude Code and switch to Cursor, Cursor will see the generated `04.Coding/` docs and resume from where you left off.
+- **Resumption**: If you start a task in Claude Code and switch to Cursor, Cursor will see the generated `AK-Docs/04.Coding/` docs and resume from where you left off.
 
 ### 2. Gemini CLI
 Pass `GEMINI.md` as system instructions to your Gemini session.
@@ -37,7 +37,7 @@ Copilot uses `.github/copilot-instructions.md` to guide its suggestions.
 The "Secret Sauce" of `ai-flow-kit` is its file-based state management:
 
 1. **Context**: Saved in `.aiflow/context/current.json`.
-2. **Progress**: Saved as Markdown docs in `04.Coding/<section>/[functionId]/[ticketId].md`.
+2. **Progress**: Saved as Markdown docs in `AK-Docs/04.Coding/<section>/[functionId]/[ticketId].md`.
 3. **Rules**: Saved in `.rules/`.
 
 Because these are standard files, any AI tool can read them. You can:

package/docs/common/workflows/bug-fix.md

@@ -17,7 +17,7 @@ AI will **automatically**:
 2. Read source code — trace data flow related to the bug
 3. Use `superpowers:systematic-debugging` to form root cause hypothesis
 4. Ask clarifying questions if reproduction steps are unclear
-5. Output `04.Coding/01.Requirements/[functionId]/[ticketId].md` containing:
+5. Output `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md` containing:
    - Bug analysis (current vs expected behavior)
    - **Root cause hypothesis** with evidence from source code
    - **Proposed fix approach** (with alternatives if applicable)
@@ -84,7 +84,7 @@ AI performs in the following order:
 AI runs:
 1. `superpowers:verification-before-completion` — all tests PASS (including old tests)
 2. `impact-analysis` — fix doesn't cause new bugs elsewhere
-3. Create `04.Coding/04.Reviews/[functionId]/[ticketId].md`
+3. Create `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md`
 
 **If OK, type:**
 ```

package/docs/common/workflows/feature.md

@@ -16,7 +16,7 @@ AI will **automatically**:
 1. Load ticket info from Backlog/Jira
 2. Read source code — understand architecture, related files, patterns
 3. Ask clarifying questions if anything is unclear (one at a time)
-4. Output `04.Coding/01.Requirements/[functionId]/[ticketId].md` containing:
+4. Output `AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md` containing:
    - Requirements summary (AI's understanding)
    - Source code analysis (related files, data flow)
    - **Proposed solution** with options and recommendation
@@ -83,7 +83,7 @@ AI runs:
 1. `superpowers:verification-before-completion` — all tests PASS
 2. `impact-analysis` — no breaking changes outside of scope
 3. Review checklist — all items ticked
-4. Create `04.Coding/04.Reviews/[functionId]/[ticketId].md`
+4. Create `AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md`
 
 AI displays summary and waits for developer review.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@relipa/ai-flow-kit",
-  "version": "0.1.5-beta.1",
+  "version": "0.1.5",
   "description": "All-in-one AI Flow Kit for team development with Claude AI - skills, templates, and MCP adapters",
   "author": "Example Team",
   "publishConfig": {

package/scripts/docs-repo.js

@@ -0,0 +1,49 @@
+const fs = require('fs-extra');
+const path = require('path');
+const chalk = require('chalk');
+const { execSync } = require('child_process');
+
+// AK-Docs (per-project docs) and Shared-Docs (cross-project templates) are
+// fixed-name folders living directly under the workspace root — the folder
+// opened in the editor, which contains one or more source repos plus these
+// two docs repos as siblings. `ak` is run from that root, so projectDir
+// (process.cwd()) already IS the root — see docs/internal/Project-Structure.md.
+const DOC_REPOS = [
+    { name: 'AK-Docs', purpose: 'tài liệu dự án (Requirements, Specs, Test Cases, Coding docs...)' },
+    { name: 'Shared-Docs', purpose: 'template dùng chung cho tất cả dự án (Spec, QA, Test Case, Test Report...)' },
+];
+
+function resolveDocsRepoPath(projectDir, repoName) {
+    return path.join(projectDir, repoName);
+}
+
+async function syncDocsRepo(projectDir, repoName, purpose) {
+    const repoPath = resolveDocsRepoPath(projectDir, repoName);
+
+    if (!(await fs.pathExists(repoPath))) {
+        console.log(chalk.yellow(`⚠ ${repoName}/ chưa tồn tại tại ${repoPath} (${purpose}). Hãy clone repo này vào thư mục root.`));
+        return;
+    }
+
+    if (!(await fs.pathExists(path.join(repoPath, '.git')))) {
+        console.log(chalk.yellow(`⚠ ${repoName}/ tồn tại tại ${repoPath} nhưng không phải git repo — bỏ qua pull.`));
+        return;
+    }
+
+    console.log(chalk.cyan(`\n⟳ Pulling latest ${repoName}...`));
+    try {
+        execSync('git pull', { cwd: repoPath, stdio: 'inherit' });
+        console.log(chalk.green(`✓ ${repoName} đã cập nhật mới nhất.`));
+    } catch (err) {
+        console.log(chalk.red(`✗ Không thể pull ${repoName}: ${err.message}`));
+    }
+}
+
+async function syncDocsRepos(projectDir) {
+    console.log(chalk.blue('\nĐồng bộ AK-Docs / Shared-Docs...'));
+    for (const repo of DOC_REPOS) {
+        await syncDocsRepo(projectDir, repo.name, repo.purpose);
+    }
+}
+
+module.exports = { syncDocsRepos, resolveDocsRepoPath, DOC_REPOS };

package/scripts/hooks/session-start.js

@@ -215,16 +215,16 @@ function buildContextPrompt(ctx, taskState) {
 
         if (currentGate === 2) {
             lines.push('Gate 1 is already APPROVED. The requirement document is at:');
-            lines.push(`  04.Coding/01.Requirements/[functionId]/${ctx.taskId}.md`);
-            lines.push(`  ([functionId] — look it up in 04.Coding/00.Overview/_Index.md or the folder containing ${ctx.taskId}.md)`);
+            lines.push(`  AK-Docs/04.Coding/01.Requirements/[functionId]/${ctx.taskId}.md`);
+            lines.push(`  ([functionId] — look it up in AK-Docs/04.Coding/00.Overview/_Index.md or the folder containing ${ctx.taskId}.md)`);
             lines.push('');
             lines.push('Proceed to Gate 2: create the implementation plan.');
             lines.push(buildModeInstruction(mode, 2));
         } else if (currentGate === 3) {
             lines.push('Gates 1 and 2 are already APPROVED. Plans are at:');
-            lines.push(`  04.Coding/01.Requirements/[functionId]/${ctx.taskId}.md`);
-            lines.push(`  04.Coding/02.Plans/[functionId]/${ctx.taskId}.md`);
-            lines.push(`  ([functionId] — look it up in 04.Coding/00.Overview/_Index.md)`);
+            lines.push(`  AK-Docs/04.Coding/01.Requirements/[functionId]/${ctx.taskId}.md`);
+            lines.push(`  AK-Docs/04.Coding/02.Plans/[functionId]/${ctx.taskId}.md`);
+            lines.push(`  ([functionId] — look it up in AK-Docs/04.Coding/00.Overview/_Index.md)`);
             lines.push('');
             lines.push('Proceed to Gate 3: implement code following the plan (TDD).');
             lines.push(buildModeInstruction(mode, 3));
@@ -251,16 +251,16 @@ function buildContextPrompt(ctx, taskState) {
             lines.push('- Pre-flight: determine functionId first (from context / input UC Spec file / ask DEV to confirm) — see the DEV workflow Pre-flight step');
             lines.push('- Read ticket + identify changed files only (no deep source scan)');
             lines.push('- Skip Q&A unless there is a critical blocking ambiguity');
-            lines.push('- Output a lite requirement doc (Sections 1, 3, 5 only) to 04.Coding/01.Requirements/[functionId]/' + ctx.taskId + '.md');
+            lines.push('- Output a lite requirement doc (Sections 1, 3, 5 only) to AK-Docs/04.Coding/01.Requirements/[functionId]/' + ctx.taskId + '.md');
             lines.push('- Target: Gate 1 complete in < 5 minutes');
         } else {
             lines.push('Gate 1 process:');
-            lines.push('0. Pre-flight: determine functionId (from context / input UC Spec file / ask DEV to confirm) + ensure 04.Coding/ tree exists — see the DEV workflow Pre-flight step. DO NOT continue without functionId.');
+            lines.push('0. Pre-flight: determine functionId (from context / input UC Spec file / ask DEV to confirm) + ensure AK-Docs/04.Coding/ tree exists — see the DEV workflow Pre-flight step. DO NOT continue without functionId.');
             lines.push('1. Read the ticket context above');
             lines.push('2. Read CLAUDE.md — understand project architecture and conventions');
             lines.push('3. Read source code — identify related files, data flow, patterns');
             lines.push('4. If anything is unclear — ask ONE question at a time');
-            lines.push('5. Output 04.Coding/01.Requirements/[functionId]/' + ctx.taskId + '.md');
+            lines.push('5. Output AK-Docs/04.Coding/01.Requirements/[functionId]/' + ctx.taskId + '.md');
             lines.push('6. Display GATE 1 prompt and wait for APPROVED');
         }
 

package/scripts/init.js

@@ -3,6 +3,7 @@ const path = require('path');
 const os = require('os');
 const chalk = require('chalk');
 const { input, checkbox, confirm } = require('@inquirer/prompts');
+const { syncDocsRepos } = require('./docs-repo');
 
 const PKG_DIR = path.join(__dirname, '..');
 const GLOBAL_AIFLOW_DIR = path.join(os.homedir(), '.aiflow');
@@ -752,7 +753,6 @@ async function ensureAiflowGitignored(projectDir) {
     const gitignorePath = path.join(projectDir, '.gitignore');
     const entries = [
         '.aiflow/',
-        'plan/',
         '.claude/',
         '.rules/',
         '.mcp.json',
@@ -1048,6 +1048,9 @@ async function init(options) {
     try {
         console.log(chalk.blue(`Initializing ai-flow-kit (v${PKG_VERSION})...`));
 
+        // ── Sync AK-Docs / Shared-Docs sibling repos ──────────────────
+        await syncDocsRepos(projectDir);
+
         // ── Auto-detect or prompt for framework if not supplied ──────
         if (frameworks.length === 0) {
             const stateFilePath = path.join(aiflowDir, 'state.json');

package/scripts/prompt.js

@@ -25,7 +25,7 @@ AI must:
 1. Load ticket context + read source code related to the bug
 2. Trace data flow to form root cause hypothesis (\`superpowers:systematic-debugging\`)
 3. If unclear → ask ONE question at a time, wait for reply
-4. Output \`plan/[ticket-id]/requirement.md\` with:
+4. Output \`AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md\` with:
    - Bug analysis (current vs expected behavior)
    - Root cause hypothesis with evidence from source code
    - Proposed fix approach (options if multiple)
@@ -52,7 +52,7 @@ Only runs after Gate 2 APPROVED.
 1. \`superpowers:verification-before-completion\` — all tests PASS (including old tests)
 2. \`impact-analysis\` skill — fix doesn't cause new bugs elsewhere
 3. Tick \`custom/rules/review-checklist.md\`
-4. Create \`plan/[ticket-id]/summary.md\`
+4. Create \`AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md\`
 - Display: "GATE 4: type APPROVED or BUG: [description]"
 - Coding bug → fix → repeat Gate 4
 - Requirement bug → back to Gate 1
@@ -77,7 +77,7 @@ AI must:
 2. Investigate related files, data flow, existing patterns
 3. Propose 2-3 solution approaches using Q&A if the problem is complex
 4. If unclear → ask ONE question at a time, wait for reply
-5. Output \`plan/[ticket-id]/requirement.md\` with:
+5. Output \`AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md\` with:
    - Requirements summary (AI's understanding in technical language)
    - Source code analysis (related files, data flow, patterns)
    - Proposed solution with options (recommended + alternatives)
@@ -104,7 +104,7 @@ Only runs after Gate 2 APPROVED.
 1. \`superpowers:verification-before-completion\` — all tests PASS
 2. \`impact-analysis\` skill — no regressions
 3. Tick \`custom/rules/review-checklist.md\`
-4. Create \`plan/[ticket-id]/summary.md\`
+4. Create \`AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md\`
 - Display: "GATE 4: type APPROVED or BUG: [description]"
 - Coding bug → fix → repeat Gate 4
 - Requirement bug → back to Gate 1
@@ -129,7 +129,7 @@ AI must:
 2. **INVOKE:** \`superpowers:systematic-debugging\` — trace through all layers
 3. **INVOKE:** \`investigate-bug\` skill — trace data flow through all layers
 4. If unclear → ask ONE question at a time
-5. Output \`plan/[ticket-id]/requirement.md\` with:
+5. Output \`AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md\` with:
    - Investigation scope and approach
    - Source code analysis (all related files traced)
    - Findings with evidence (log output, code references)
@@ -156,7 +156,7 @@ AI must:
 1. Load ticket context + read source code to understand current state
 2. **INVOKE:** \`impact-analysis\` skill — map ALL callers and dependants
 3. If unclear → ask ONE question at a time
-4. Output \`plan/[ticket-id]/requirement.md\` with:
+4. Output \`AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md\` with:
    - Current state analysis (what exists, what's wrong)
    - Target state (what it should look like after refactor)
    - Proposed approach (step-by-step refactor strategy)
@@ -182,7 +182,7 @@ Only runs after Gate 2 APPROVED.
 1. \`superpowers:verification-before-completion\` — all tests PASS
 2. \`impact-analysis\` skill — verify no regressions
 3. Tick \`custom/rules/review-checklist.md\`
-4. Create \`plan/[ticket-id]/summary.md\`
+4. Create \`AK-Docs/04.Coding/04.Reviews/[functionId]/[ticketId].md\`
 - Display: "GATE 4: type APPROVED or BUG: [description]"
 
 ### GATE 5 — Peer Review & Done
@@ -203,7 +203,7 @@ AI must:
 1. Load ticket context + read source code thoroughly
 2. Map all dependencies, callers, services, jobs, tests
 3. If unclear → ask ONE question at a time
-4. Output \`plan/[ticket-id]/requirement.md\` with:
+4. Output \`AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md\` with:
    - Change description and scope
    - Dependency map (all callers, services, jobs, tests)
    - Impact level: 🟢 Low / 🟡 Medium / 🔴 High / 🔥 Critical
@@ -229,7 +229,7 @@ AI must:
 1. Load ticket context + read source code thoroughly
 2. Understand what needs to be tested (unit, integration, e2e)
 3. If unclear → ask ONE question at a time
-4. Output \`plan/[ticket-id]/requirement.md\` with:
+4. Output \`AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md\` with:
    - Test scope and strategy
    - Test cases to cover (happy path + edge cases + failure cases)
    - Source code references
@@ -239,7 +239,7 @@ AI must:
 ### GATE 2 — Implementation Plan
 **INVOKE:** \`generate-spec\` skill, then \`superpowers:writing-plans\`
 - Create detailed TDD test implementation plan.
-- Output \`plan/[ticket-id]/plan.md\`.
+- Output \`AK-Docs/04.Coding/02.Plans/[functionId]/[ticketId].md\`.
 - Display: "GATE 2 PAUSED: type APPROVED to start coding".
 
 ### GATE 3 — Write Tests (TDD)
@@ -265,7 +265,7 @@ AI must:
 1. Load ticket context + read source code
 2. Understand what needs to be documented and for whom
 3. If unclear → ask ONE question at a time
-4. Output \`plan/[ticket-id]/requirement.md\` with:
+4. Output \`AK-Docs/04.Coding/01.Requirements/[functionId]/[ticketId].md\` with:
    - Documentation scope and target audience
    - Content outline (sections to cover)
    - Source code references

package/scripts/task.js

@@ -2,12 +2,14 @@ const fs = require('fs-extra');
 const path = require('path');
 const chalk = require('chalk');
 const { confirm } = require('@inquirer/prompts');
+const { resolveDocsRepoPath } = require('./docs-repo');
 
 const PROJECT_DIR   = process.cwd();
 const AIFLOW_DIR    = path.join(PROJECT_DIR, '.aiflow');
 const CONTEXT_DIR   = path.join(AIFLOW_DIR, 'context');
 const CURRENT_FILE  = path.join(CONTEXT_DIR, 'current.json');
 const TASKS_DIR     = path.join(AIFLOW_DIR, 'tasks');
+const CODING_DIR    = path.join(resolveDocsRepoPath(PROJECT_DIR, 'AK-Docs'), '04.Coding');
 
 // ──────────────────────────────────────────────────────────────
 // Entry point
@@ -216,7 +218,7 @@ async function resetTask(taskId) {
     console.log(chalk.gray(`    Gate: ${taskState.currentGate} → 1  |  Approvals cleared  |  Status: active`));
 
     const deletePlan = planFiles.length > 0 && await confirm({
-        message: `Also delete ${planFiles.length} gate doc file(s) (04.Coding/ + legacy plan/) for ${taskId}?`,
+        message: `Also delete ${planFiles.length} gate doc file(s) (AK-Docs/04.Coding/ + legacy plan/) for ${taskId}?`,
         default: false,
     });
 
@@ -364,7 +366,7 @@ async function nextGate(taskId) {
     console.log(chalk.gray(`    1. Open a NEW chatbox or terminal session.`));
     console.log(chalk.gray(`    2. Run: aiflow task resume ${resolvedId} (to load context).`));
     console.log(chalk.gray(`    3. Type "start" or "continue from the current plan".`));
-    console.log(chalk.yellow(`       (Note: Gate 3 progress is saved via [x] checkboxes in the Gate 2 plan doc (04.Coding/02.Plans/).`));
+    console.log(chalk.yellow(`       (Note: Gate 3 progress is saved via [x] checkboxes in the Gate 2 plan doc (AK-Docs/04.Coding/02.Plans/).`));
     console.log(chalk.yellow(`        The AI will automatically resume the exact task you left off.)`));
     console.log();
 }
@@ -374,18 +376,17 @@ async function nextGate(taskId) {
 // ──────────────────────────────────────────────────────────────
 
 /**
- * Find gate output docs for a task under 04.Coding/<section>/<functionId>/<taskId>.md
+ * Find gate output docs for a task under AK-Docs/04.Coding/<section>/<functionId>/<taskId>.md
  * (new convention) plus the legacy plan/<taskId>/ folder. Returns absolute paths.
  */
 async function findTaskDocs(taskId) {
     const results = [];
 
-    const codingDir = path.join(PROJECT_DIR, '04.Coding');
-    if (await fs.pathExists(codingDir)) {
-        const sections = await fs.readdir(codingDir, { withFileTypes: true }).catch(() => []);
+    if (await fs.pathExists(CODING_DIR)) {
+        const sections = await fs.readdir(CODING_DIR, { withFileTypes: true }).catch(() => []);
         for (const section of sections) {
             if (!section.isDirectory()) continue;
-            const sectionDir = path.join(codingDir, section.name);
+            const sectionDir = path.join(CODING_DIR, section.name);
             const featureDirs = await fs.readdir(sectionDir, { withFileTypes: true }).catch(() => []);
             for (const feature of featureDirs) {
                 if (!feature.isDirectory()) continue;
@@ -442,9 +443,9 @@ async function detectCurrentGate(taskId) {
         if (state.currentGate) return state.currentGate;
     }
 
-    // New convention: 04.Coding/<section>/<functionId>/<taskId>.md
+    // New convention: AK-Docs/04.Coding/<section>/<functionId>/<taskId>.md
     const hasDocInSection = async (section) => {
-        const dir = path.join(PROJECT_DIR, '04.Coding', section);
+        const dir = path.join(CODING_DIR, section);
         if (!(await fs.pathExists(dir))) return false;
         const features = await fs.readdir(dir, { withFileTypes: true }).catch(() => []);
         for (const f of features) {

package/scripts/update.js

@@ -2,6 +2,7 @@ const fs = require('fs-extra');
 const path = require('path');
 const chalk = require('chalk');
 const { confirm, select } = require('@inquirer/prompts');
+const { syncDocsRepos } = require('./docs-repo');
 
 const PKG_DIR = path.join(__dirname, '..');
 const PKG_VERSION = require('../package.json').version;
@@ -25,6 +26,9 @@ module.exports = async function update(options = {}) {
         return;
     }
 
+    // ── Sync AK-Docs / Shared-Docs sibling repos ──────────────────
+    await syncDocsRepos(projectDir);
+
     const state = await fs.readJson(stateFile);
     const currentVersion = state.current_version;