@relipa/ai-flow-kit 0.1.9 → 0.2.0-beta.1

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

@@ -4,6 +4,7 @@
 > **Do not skip, shorten, or merge Gates.**
 
 > **Task type `gen-doc`** uses a **2-gate flow** (Gate 1 + Gate 2 only). See the gen-doc section below — do NOT run Gates 3/4/5 for gen-doc tasks.
+> **Task type `ingest-data`** also uses a **2-gate flow** — see the ingest-data section below. For PM/BrSE/Comtor ingesting customer communication (Backlog ticket/comment/Document/Wiki link, SharePoint link, or pasted text) into `AK-Docs/01.QnA/`.
 
 You have superpowers. When a ticket context exists in `.aiflow/context/current.json`:
 - **Consult the "AI Skill Registry"** below to find instructions for each skill (`SKILL.md`).
@@ -40,6 +41,7 @@ Read `.aiflow/context/current.json` → check the `taskType` field:
 | `feature`, `bug-fix`, `refactor`, `investigation`, `documentation` | **[DEV] 5-Gate Development Workflow** (below) |
 | `create-spec` | **[BA] 4-Gate Spec Creation Workflow** (below) |
 | `create-testcase` | **[QA] 4-Gate TestCase Creation Workflow** (below) |
+| `ingest-data` | **[COMTOR] Ingest Data — 2-Gate Flow** (below) |
 
 If `taskType` is missing or unrecognized, default to the DEV workflow and ask ONE clarifying question.
 
@@ -670,3 +672,65 @@ Bugs logged: [N] | Skipped: [N]
 8. Display: `GATE 2 DONE: Document generated at [path]`
 
 **Do NOT wait for extra approval before generating the document or opening the MR — only the explicit branch/MR confirmations above gate this; run the gate 2 approved command immediately after.**
+
+---
+
+## ingest-data Task Type — 2-Gate Flow
+
+> This section applies **only** when `taskType === "ingest-data"`. All other task types use the flows above.
+> **For:** PM · BrSE · Comtor ingesting customer communication into `AK-Docs/01.QnA/` — see `docs/internal/PM Workflow_v1.0.md` Flow B for the full design background.
+> **Input formats accepted:** Backlog ticket/comment link, Backlog Document link, Backlog Wiki link, Jira ticket/comment link, SharePoint link (not yet connected — see Gate 1 Step 2), or plain pasted text.
+
+**INVOKE:** `ingest-data` skill (from `.claude/skills/ingest-data/SKILL.md`) for both gates — it has the full classification rules, draft templates, and per-file format. This section only covers the gate mechanics.
+
+### GATE 1 — Fetch, Classify, Draft (auto-start)
+
+0. **Pre-flight (bắt buộc):** chạy [Pre-flight — Đồng bộ Source & Docs](#pre-flight-bắt-buộc--đồng-bộ-source--docs-đầu-mỗi-gate) ở đầu file. Lỗi → hiển thị ⚠️ cảnh báo, không dừng gate.
+1. Read `.aiflow/context/current.json` — if the primary input is a URL (Backlog/Jira/SharePoint), it's already there as `taskId`/description; if the input was plain pasted text via `ak use --manual`, it's in `description`.
+2. **Resolve the source** (see `ingest-data` skill for full detail):
+   - Backlog/Jira ticket, comment, Document, or Wiki URL → run `ak fetch-links "<url>"`, parse the JSON.
+   - SharePoint URL → `ak fetch-links` returns `{ sourceType: "unsupported" }` (no connector yet — Microsoft Graph API/OAuth not built). Tell the user to paste the comment/document text directly instead of the link.
+   - Plain text → use as-is, no fetch needed.
+3. **Classify** into `QnA-Log.md` / `Meetings-Log.md` / `Confirmations-Log.md` per the `ingest-data` skill's rules. If ambiguous (especially Confirmations — the rule for "official confirm" vs "regular feedback" is not yet finalized, see PM Workflow doc Vấn đề còn mở #1) — **ask the user**, do not guess silently.
+4. Draft the entry using the exact template for the target log file (skill has all 3 templates) — include the trace fields (`Nguồn`, `functionId`, `Người tổng hợp`, `Người approve tại nguồn`).
+5. Display the draft in full (not summarized) plus this footer:
+   ```
+   ⏸️ INGEST DRAFT READY — cần bạn review trước khi mở MR
+
+   Nguồn: [mô tả ngắn](url hoặc "pasted text")
+   Ghi vào: AK-Docs/01.QnA/[QnA-Log.md | Meetings-Log.md | Confirmations-Log.md]
+
+   → Xem draft đầy đủ ở trên
+   → Gõ APPROVED để tạo branch + MR (Gate 2)
+   → Hoặc yêu cầu sửa trực tiếp draft, AI sẽ cập nhật lại rồi hiển thị lại
+   ```
+6. Loop on edits until the user types **APPROVED** — do not proceed to Gate 2 before that.
+
+> **Telemetry:** Run `ak gate 1 start --ticket [ticket-id]` when starting. Run `ak gate 1 approved --ticket [ticket-id]` when APPROVED is received.
+
+### GATE 2 — Branch + Merge Request (runs immediately after APPROVED)
+
+1. Xác định `functionId`: tag đọc được từ Backlog Document (nếu có) → suy từ input → không suy được thì dùng `general` (theo đúng quy ước `custom/rules/project-conventions.md`, tương tự gen-doc dùng `AD-HOC`).
+2. Kiểm tra `AK-Docs` hiện đang ở branch nào (`git -C AK-Docs branch --show-current`). Nếu chưa ở `feature/[functionId]/[ticketId]` → hỏi: "Chưa có branch riêng cho task này. Tạo branch `feature/[functionId]/[ticketId]` từ `main` — đồng ý không?" → đồng ý thì chạy `ak docs branch [functionId] [ticketId] --yes`; từ chối thì tiếp tục trên nhánh hiện tại. ❌ Không tự thêm `--yes` khi chưa thấy xác nhận rõ ràng.
+3. Ghi/append entry đã approve vào đúng file log (tạo file + header template nếu chưa tồn tại).
+4. Soạn title + description cho MR (tóm tắt entry vừa ghi, link nguồn gốc), hiển thị cho người dùng xem trước. Hỏi: "Nội dung commit/MR như trên — đồng ý submit AK-Docs không?" → đồng ý thì chạy `ak docs submit --title "..." --description "..." --yes`; từ chối thì dừng, để người dùng tự commit khi sẵn sàng. ❌ Không tự thêm `--yes` khi chưa thấy xác nhận rõ ràng.
+5. Thông báo: MR đã mở, chờ **PM review & merge vào `main`** — đây là bước duyệt cuối cùng, không phải tự merge.
+6. Run: `ak gate 2 approved --ticket [ticket-id]` to close the task.
+7. Display: `GATE 2 DONE: Entry ghi vào AK-Docs/01.QnA/[file] — MR: [url hoặc "tạo thủ công"]`
+
+> **Telemetry:** Run `ak gate 2 start --ticket [ticket-id]` when starting. Run `ak gate 2 approved --ticket [ticket-id]` when Gate 2 completes.
+
+### GATE 3 — Sinh Task & Tạo Ticket (auto, chạy ngay sau Gate 2 xong)
+
+> Implements "Vấn đề 5" trong `docs/internal/PM Workflow_v1.0.md`. **Không chờ APPROVED để bắt đầu** — chạy tự động ngay sau Gate 2 Bước 7, không cần lệnh riêng và không cần chờ PM merge MR (merge là việc độc lập của PM). `INVOKE`: `ingest-data` skill § 5 cho toàn bộ logic phân tích/đề xuất — mục này chỉ nêu gate mechanics.
+
+1. Đọc lại entry vừa ghi + điều tra source/docs liên quan (skill § 5.1).
+2. Quyết định content này có cần task không (skill § 5.2). Nếu KHÔNG cần task → hiển thị thông báo tương ứng và **kết thúc luôn, không chạy `ak gate 3 start`, không có Gate 3 Display**.
+3. Nếu CẦN task → chạy `ak gate 3 start --ticket [ticket-id]`, rồi đề xuất danh sách task (skill § 5.3), cho PM sửa/thêm/xoá (skill § 5.4), lặp tới khi PM hài lòng.
+4. Điểm dừng xác nhận trước khi tạo ticket (skill § 5.5) — ❌ không tự thêm `--yes`, phải có xác nhận rõ ràng trong hội thoại.
+5. Xác định project đích trên Backlog/Jira (skill § 5.6, dùng `ak backlog-projects`/`ak jira-projects` + `ak backlog-set-default-project`/`ak jira-set-default-project`).
+6. Tạo ticket bằng `ak tasks create-tickets <file>.json --json` (skill § 5.7). Nếu thiếu WRITE credentials, hỏi PM nhập ngay trong chat rồi `ak credentials set <field> "<value>"` và thử lại đúng 1 lần.
+7. Ghi ngược link ticket vào entry gốc + hiển thị tổng kết (skill § 5.8).
+8. Run: `ak gate 3 approved --ticket [ticket-id]` để đóng task.
+
+> **Telemetry:** Run `ak gate 3 start --ticket [ticket-id]` chỉ khi Bước 2 kết luận CẦN task. Run `ak gate 3 approved --ticket [ticket-id]` khi Gate 3 hoàn tất.

package/docs/common/BA-Specs-Structure.md

@@ -15,6 +15,7 @@
 ├── 00.Requirements/                    # Requirements Gathering
 │   └── F-001_User-Login/
 │       ├── Raw-Requirements_v1.md      # Raw input: ticket, meeting note, email
+│       ├── System-Requirement_v2.md    # Dev-facing bridge doc (create-system-requirement task type)
 │       └── assets/                     # Images, attachments, recordings
 │
 ├── 01.Analysis/                        # Gate 1: Business Analysis
@@ -46,6 +47,7 @@
 | Section folder | `{N}.{Pascal-Case}/` | `00.Requirements/`, `03.UI-Prototypes/` |
 | Feature folder | `F-{3-digit}_{Pascal-Case}/` | `F-001_User-Login/` |
 | Requirements file | `Raw-Requirements_v{N}.md` | `Raw-Requirements_v1.md` |
+| System Requirement file | `System-Requirement_v{N}.md` | `System-Requirement_v2.md` |
 | Analysis file | `Analysis_v{N}.md` | `Analysis_v2.md` |
 | QnA file | `QnA-Log_v{N}.md` | `QnA-Log_v1.md` |
 | Prototype file | `UI-Prototype_v{N}.html` | `UI-Prototype_v1.html` |
@@ -84,3 +86,4 @@
 - Thông báo cho Dev + Tester sau khi UC Spec sẵn sàng
 - Không xóa file cũ — move vào `_archive/` khi có version mới
 - `02.QnA/` là Q&A nội bộ với stakeholder — khác với `01.QnA/` ngoài dự án (dành cho khách hàng)
+- `System-Requirement_v{N}.md` trong `00.Requirements/` do Dev viết (task type `create-system-requirement`, chạy 1 lần/functionId/UC Spec version), không phải do BA — `N` khớp đúng version của `UC-Spec_v{N}.md` mà nó trace tới, không phải bộ đếm riêng

package/docs/common/CHANGELOG.md

@@ -7,6 +7,45 @@ Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ---
 
+## [0.2.1] - 2026-08-05
+
+### Added
+
+- **`ingest-data` gained Gate 3 — auto-triggered task proposal & real ticket creation on Backlog/Jira, closing the gap after Gate 2 where the flow used to just stop once an entry landed in `AK-Docs/01.QnA/`.** Implements "Vấn đề 5" in `docs/internal/PM Workflow_v1.0.md`, decided to run **automatically** right after Gate 2 (not on-demand as the doc's earlier tentative proposal had it):
+  - AI re-reads the entry just ingested plus related source code/docs to judge impact, then decides whether it needs a task at all — pure-reference content (FYI, status update) ends the gate with no task proposed, no ticket created.
+  - When action is needed, proposes a task list (`type`: spec/coding/test/other, `title`, `track`, `description` built from the PM Workflow §6.1 template — spec-type tasks additionally require a PM-supplied "Nguồn tham chiếu" link, never inferred). The user can add/edit/remove tasks directly during review — not just approve/reject the whole list — before the single explicit confirmation point ("Danh sách task như trên — đồng ý tạo trên Backlog/Jira?", never auto-`--yes`'d).
+  - New `scripts/ticket-writer.js` — `ak tasks create-tickets <file>.json [--json]` posts the approved list as real Backlog/Jira issues. `scripts/link-resolver.js` gained the write-side API calls it needed (`createBacklogIssue`, `createJiraIssue`, `fetchBacklogIssueTypes`, `fetchBacklogPriorities`) plus a generic `httpsPost` helper (form-encoded for Backlog, JSON for Jira) — the existing `httpsGet`-only file had no POST capability before this.
+  - **Deliberately separate WRITE credentials** (`BACKLOG_API_KEY_WRITE` / `JIRA_API_TOKEN_WRITE`) from the read-only keys `ak fetch-links`/`ak use` already rely on, per the PM Workflow doc's policy of never letting the read key create tickets. When missing, `ak tasks create-tickets` returns a structured `{"error":"missing-write-credentials", field, message}` instead of failing silently — the AI surfaces this in chat, asks the user to paste the key, saves it via the new `ak credentials set <key> <value>` (allowlisted to the keys this feature introduced — dedicated adapter credentials still go through `ak init --adapter`), and retries once.
+  - Project-id resolution reuses the existing `BACKLOG_DEFAULT_PROJECT_ID`/`ak backlog-projects`/`ak backlog-set-default-project` pattern; added the Jira equivalents (`ak jira-projects`, `ak jira-set-default-project`, `fetchJiraProjects` in `scripts/use.js`) so both adapters check local config before ever prompting.
+  - Approved tickets get their link written back into the originating `Meetings-Log`/`QnA-Log`/`Confirmations-Log` entry (`→ Tasks created: TICKET-101 (coding), ...`), keeping the traceability chain from PM Workflow §6 intact end-to-end.
+  - **Still open, tracked in the PM Workflow doc's Vấn đề 5 implementation note:** no fixed feedback→task-type rule table (AI still judges per-context); new tickets don't auto-attach `functionId`/labels (Dev/BA/QA still assign on `ak use TICKET-XXX`); Backlog issueType/priority default to the project's first issueType and a "Normal"-named priority unless overridden explicitly in the task JSON.
+
+## [0.2.0] - 2026-08-04
+
+### Added
+
+- **`create-system-requirement` — new task type, bridging UC Spec (BA) into a Dev-facing System Requirement.** Until now, "System Requirement" only existed as whatever a coding ticket's Gate 1 (`read-study-requirement`) happened to write into its own per-ticket `requirement.md` — no single document traced 1-1 to a UC Spec version, so N tickets under one `functionId` (including bug fixes) left no coherent, BA-reviewable picture of what the system as a whole is required to do. New skill `custom/skills/create-system-requirement/SKILL.md` runs as its own 2-gate task type, scoped to a `functionId` (not a ticket):
+  - **Gate 1 — Investigate UC & Draft:** resolve the current UC Spec version, investigate existing source code/error-handling conventions (same methodology as `read-study-requirement`, including the GitNexus MCP shortcut), translate every Main/Alternative/Exception Flow step and Business Rule into Functional/Non-Functional Requirements, Validation Rules, Exception & Error Handling, and Acceptance Test scenarios (Given/When/Then) — every item carries a traced UC reference, nothing is invented. Q&A loops one question at a time until every Fact/Assumption/Gap is Confirmed; a genuinely unanswerable Gap blocks progress to Gate 2 rather than being guessed.
+  - **Gate 2 — Finalize & Approve:** decide single-file vs. split (default is one file, mirroring the UC Spec 1-1; splits only on measurable signals — business-rule domain fan-out, module/service fan-out, flow-count overload, or a ~400-line size ceiling, always along a semantic seam, never by raw line count; a UC Spec that reads like 2+ bundled independent use cases is escalated back to BA instead of silently split), write `AK-Docs/04.Coding/01.Requirements/[functionId]/System-Requirement_v{N}.md` (`N` pinned to the UC Spec version it was traced against, carried in a mandatory `UC-Spec-Version` header), and wait for `APPROVED`.
+  - Selectable via `ak use`'s "Task type:" prompt ("📐 Create System Requirement") or auto-detected by `aiflow prompt` — added to `scripts/detect.js` (keywords), `scripts/use.js` (both task-type selectors), and `scripts/task.js` (`maxGate = 2`, custom gate labels, alongside `gen-doc`'s existing 2-gate handling).
+- **Coding Gate 1 (`read-study-requirement`) now requires System Requirement to exist and match the current UC Spec version before it can run.** New blocking Step 0: resolves the ticket's `functionId`, locates its current UC Spec, and checks for a `System-Requirement_v*.md` whose `UC-Spec-Version` header matches. Missing or stale → Gate 1 cancels outright and tells DEV to run the new `create-system-requirement` task type first (`⏸️ Gate 1 cancelled — run "ak use" and pick "📐 Create System Requirement" for [functionId] first...`); this check runs even in Fast Track mode (it's a 2-file header check, not a heavy investigation). Root `CLAUDE.md`'s Gate 1 section gained a matching "0. Pre-check (blocking)" line.
+  - Once unblocked, Step 1 now reads the System Requirement as mandatory input (`FR-*`/`NFR-*`/`VR-*`/`ER-*` item IDs are referenced, not restated), and a new **Step 3.5 — Reconcile with System Requirement** requires every ticket's scope to trace to an existing item, a UC-Spec-backed case System Requirement missed (proposed as a diff for DEV to confirm, appended with a Change Log row — never written directly, never bumping `System-Requirement-Version`), or a stop-and-ask when a ticket's scope traces to neither document at all.
+- **Memory recall now has a profile for `create-system-requirement`.** `scripts/hooks/session-start.js`'s `inferWorkflow()` previously had no mapping for this task type (it would fall through to `null` → the generic `gen-doc` default), so memory entries tagged for it would never score the `workflows`-match bonus in `memory-store.js`'s `scoreMemory()`. Added the mapping, plus a guidance row in `docs/common/Memory-Architecture-v1.0.md`'s workflow-profile table (§5.2) — `domain` + `glossary` + `architecture`/`lessons-dev` + related `decisions` — since this task type bridges BA business language and Dev technical convention rather than sitting fully in either camp.
+- **`ingest-data` — new task type for PM/BrSE/Comtor, ingesting customer communication into `AK-Docs/01.QnA/`.** Until now the only way link/text content from Backlog or SharePoint reached `AK-Docs` was a developer manually editing `QnA-Log.md` — no fetch, no classification, no drafted trace fields. New skill `custom/skills/ingest-data/SKILL.md`, wired as a 2-gate task type in `custom/templates/shared/gate-workflow.md`:
+  - **Gate 1 — Fetch, Classify, Draft:** resolves the source (Backlog ticket/comment/Document/Wiki link, Jira ticket/comment link, SharePoint link, or plain pasted text — via `ak fetch-links`, see below), classifies it into `QnA-Log.md` / `Meetings-Log.md` / `Confirmations-Log.md`, and drafts the entry with trace fields (`Nguồn`, `functionId`, `Người tổng hợp`, `Người approve tại nguồn`). When the target log is ambiguous — most notably Confirmations vs. regular feedback, a rule PM has not yet finalized (see `docs/internal/PM Workflow_v1.0.md` "Vấn đề còn mở" #1) — it asks instead of guessing. Displays the full draft (never summarized) and loops on edits until `APPROVED`.
+  - **Gate 2 — Branch + Merge Request:** writes the approved entry to `AK-Docs/01.QnA/{QnA-Log,Meetings-Log,Confirmations-Log}.md` (creating the file with its header template if it doesn't exist yet), then reuses the existing `ak docs branch`/`ak docs submit` (no new Git-writing code) behind the same explicit-confirmation gate every other docs-writing flow uses.
+  - Selectable via `ak use`'s "Task type:" prompt ("📥 Ingest Data" — new `PM` category). Output paths documented in `custom/rules/project-conventions.md` as a new, flat (non-`[functionId]/[ticketId]`) section, since these are project-wide logs, not per-ticket documents.
+  - Deliberately keeps `AK-Docs/01.QnA/` as the folder name rather than renaming to `01.Communications/` per the still-undecided proposal in `docs/internal/PM Workflow_v1.0.md` §1 — avoids a breaking rename on projects already using `01.QnA/QnA-Log.md` (e.g. the `ast-ai-agent` pilot). `docs/common/Docs-Management-Flow.md` §3's scope table now explicitly lists `01.QnA/` alongside `02.BA-Specs/`/`03.Testing/`/`04.Coding/`/`99.Memory/` as requiring the branch+MR flow.
+- **`link-resolver.js` / `ak fetch-links` now fetch Backlog Document and Wiki links, not just ticket/comment — built for `ingest-data`, reusable anywhere.** `classifyLink()` gained a `kind` field (`ticket` | `document` | `wiki` | `unsupported`) and two new URL patterns: Backlog Document permalinks (`/document/{id}`, `/alias/document/{id}#comment-{id}`) and Wiki permalinks (`/alias/wiki/{id}`). New fetchers `fetchBacklogDocument`, `fetchBacklogDocumentComment`, `fetchBacklogWiki` call the same read-scoped `BACKLOG_API_KEY` already used for tickets — no new credentials needed. ⚠️ The Document API (`/api/v2/documents/:id`) is a genuinely new Nulab endpoint (added 2026) and its exact path has **not been verified against a live Backlog space** — expect to adjust it if it 404s. Also added `SHAREPOINT_RE` so a `*.sharepoint.com` URL is recognized and returns a clear `{ sourceType: "unsupported", reason: "sharepoint-not-configured" }` stub (with guidance to paste text instead) rather than the generic "not a recognized URL" error — SharePoint still has no real connector (Microsoft Graph API/OAuth is unbuilt, see `docs/internal/PM Workflow_v1.0.md` "Vấn đề 4").
+  - Auto-resolution of links found inside a ticket description (`ak use`'s `resolveLinks`, capped at 5) is **unchanged in scope** — `scanLinks()` now explicitly filters to `kind === 'ticket'` only, so Document/Wiki/SharePoint links are never auto-fetched en masse, only via an explicit single `ak fetch-links <url>` call.
+- **`ak use` now captures `projectId`/`projectKey` from the loaded Backlog/Jira ticket.** `buildContextFromBacklog`/`buildContextFromJira` in `scripts/use.js` read `issue.projectId` (Backlog) and `fields.project.id`/`fields.project.key` (Jira), falling back to parsing the key out of the ticket ID (`PROJ-33` → `PROJ`) via a new `projectKeyFromIssueKey()` helper. Persisted into `.aiflow/context/current.json` and `.aiflow/state.json` (`current_context_project_id`/`current_context_project_key`), and shown in the `ak use` summary output. This is a read-only, informational addition — no code yet uses it to pick a Backlog/Jira project when creating a new ticket (that remains future work, tracked as "Vấn đề 5.1" in the PM Workflow doc).
+
+### Fixed
+
+- **`ak use`'s "Task type:" selector crashed on every invocation once "📐 Create System Requirement" was added to the list.** `td()` (`scripts/use.js`) looks up `CATEGORY_COLOR[cat]` and calls it as a chalk styling function; the `"Dev"` category used by the Create System Requirement entry had no entry in `CATEGORY_COLOR`, so building the choices array threw `TypeError: CATEGORY_COLOR[cat] is not a function` before the prompt could even render — meaning `ak use <ticket>` and `ak use --manual` were both broken outright. Added `Dev` (and `PM`, for the new `ingest-data` entry) to `CATEGORY_COLOR`.
+
+---
+
 ## [0.1.9] - 2026-08-04
 
 ### Added

package/docs/common/Docs-Management-Flow.md

@@ -38,7 +38,7 @@
 
 | Repo | Nội dung | Áp dụng flow này? |
 |---|---|---|
-| `AK-Docs` | `02.BA-Specs/`, `03.Testing/`, `04.Coding/`, `99.Memory/` — tài liệu riêng của từng dự án | ✅ Bắt buộc |
+| `AK-Docs` | `01.QnA/`, `02.BA-Specs/`, `03.Testing/`, `04.Coding/`, `99.Memory/` — tài liệu riêng của từng dự án | ✅ Bắt buộc |
 | `Shared-Docs` | Template dùng chung mọi dự án | ✅ Áp dụng, nhưng approver cuối có thể là AI Testing Team thay vì PM dự án (giống Flow B của Memory-Architecture) — mỗi dự án tự quyết định khi setup |
 
 Flow này **không áp dụng** cho source code repo (Dev vẫn tạo PR code theo quy trình hiện có ở Gate 5 — `superpowers:requesting-code-review`). Đây là flow riêng cho kho **tài liệu**.

package/docs/common/INDEX.md

@@ -28,6 +28,7 @@
 | `AK-Docs/03.Testing/` folder structure (Tester) | [Testing-Structure.md](./Testing-Structure.md) | Strategies → Testcases → evidence, by Function-ID |
 | `99.Memory/` Project Brain — full design, scoring model, mem-id scheme, role/PM permissions | [Memory-Architecture-v1.0.md](./Memory-Architecture-v1.0.md) | v1.1 — Phase 1 (`draft/list/submit/remove`) is what's implemented today; later phases in this doc are roadmap, not shipped yet |
 | How updates to `AK-Docs`/`Shared-Docs` get reviewed — branch/Merge Request flow, who can merge to `main` | [Docs-Management-Flow.md](./Docs-Management-Flow.md) | Doc's own header says `Trạng thái: Draft — chờ PM review` — flag that when answering, don't present it as final policy |
+| PM/BrSE/Comtor — ingest a Backlog/Jira/SharePoint link or pasted text into `AK-Docs/01.QnA/` | [Project-Structure.md](./Project-Structure.md) (§ `01.QnA/`), `.claude/skills/ingest-data/SKILL.md` | `ak use` → taskType `ingest-data`, 2-gate flow (fetch/classify/draft → branch+MR). SharePoint link fetch is **not connected yet** — falls back to pasted text |
 
 ## Unanswered topics (do not invent — say so and stop here)
 

package/docs/common/Memory-Architecture-v1.0.md

@@ -449,6 +449,7 @@ score = 3 × match(memory nằm trong folder functionId của ticket)
 | coding — Gate 1–5 | `architecture` functionId liên quan + `lessons/dev` + `instincts` + `decisions` technical |
 | create-spec | `domain` + `glossary` + `lessons/ba` + `decisions` business liên quan |
 | create-testcase / execute-test | `lessons/qa` + `domain` + `glossary` |
+| create-system-requirement | `domain` + `glossary` (hiểu đúng thuật ngữ nghiệp vụ từ UC Spec) + `architecture` functionId liên quan + `lessons/dev` (convention lỗi/exception hiện có) + `decisions` liên quan — bridge cả 2 phía BA/Dev, không rơi hẳn về 1 bên |
 | gen-doc / không xác định (mặc định) | `decisions` + `03.Retro` gần nhất + `architecture` functionId liên quan |
 
 **Điều chỉnh lượng theo độ phức tạp task:** ticket chạm nhiều module/mô tả dài → tăng N (10→15); hotfix nhỏ → giảm N (10→5) nhưng ưu tiên tuyệt đối lessons của đúng module; bug fix → bơm thêm toàn bộ lessons trong folder functionId liên quan (`01.Lessons/*/<functionId>/`) kể cả vượt N.

package/docs/common/Project-Structure.md

@@ -38,8 +38,10 @@ AK-Docs/
 │   ├── Function-List.md                # F-ID | Feature | BA | Dev | Tester | Status
 │   └── Team.md                         # Member, role, contact
 │
-├── 01.QnA/                             ← Trao đổi với khách hàng (có comtor)
-│   └── QnA-Log.md                      # 1 file duy nhất cho toàn dự án
+├── 01.QnA/                             ← Trao đổi với khách hàng (có comtor/BrSE)
+│   ├── QnA-Log.md                      # Hỏi-đáp thông thường — 1 file duy nhất cho toàn dự án
+│   ├── Meetings-Log.md                 # Tổng hợp meeting minutes (taskType `ingest-data`) — tạo khi cần
+│   └── Confirmations-Log.md            # Mốc khách CHỐT chính thức (taskType `ingest-data`) — tạo khi cần
 │
 ├── 02.BA-Specs/                        ← BA quản lý
 │   ├── 00.Requirements/                # Requirements Gathering
@@ -102,6 +104,7 @@ Mỗi dự án khi cần tạo tài liệu mới (UC Spec, Test Case, Test Repor
 |---|---|---|
 | PM / BrSE | `00.Project-Overview/` | Đầu dự án + mỗi sprint |
 | BA / PM / Comtor | `01.QnA/QnA-Log.md` | Khi có câu hỏi từ khách hàng |
+| PM / BrSE / Comtor | `01.QnA/Meetings-Log.md`, `Confirmations-Log.md` | Ingest link/text đã approve, qua taskType `ingest-data` (`ak use` → "📥 Ingest Data") |
 | BA | `02.BA-Specs/` | Sau khi Gate 4 APPROVED |
 | Tester | `03.Testing/` | Sau khi Gate 4 APPROVED |
 | Dev | `04.Coding/` | Trước khi tạo Pull Request |

package/package.json

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

package/scripts/create-score-excel.js

@@ -24,25 +24,6 @@ function norm(cmd) {
   return ALIAS_MAP[c] || c;
 }
 
-// ── Version helpers ─────────────────────────────────────────────────────────
-const CURRENT_VERSION = '0.1.6';
-
-function parseVersion(v) {
-  if (!v || v === '-' || v === '' || v.toLowerCase() === 'unknown') return null;
-  const core = v.split('-')[0]; // strip prerelease suffix, e.g. 0.1.5-beta.1 -> 0.1.5
-  const parts = core.split('.').map(n => parseInt(n, 10));
-  if (parts.some(n => Number.isNaN(n))) return null;
-  return parts;
-}
-
-function compareVersion(a, b) {
-  for (let i = 0; i < Math.max(a.length, b.length); i++) {
-    const diff = (a[i] || 0) - (b[i] || 0);
-    if (diff !== 0) return diff;
-  }
-  return 0;
-}
-
 // ── Parse log file ─────────────────────────────────────────────────────────
 function parseLog(filePath) {
   const lines = fs.readFileSync(filePath, 'utf-8').split(/\r?\n/);
@@ -58,19 +39,17 @@ function parseLog(filePath) {
     if (!user || user === '-' || user === '') continue;
 
     const timestamp = cols[0] || '';
-    const version = cols[5] || '';
     const command = cols[6] || '';
     const ticket = cols[9] || '';
 
     const date = timestamp.split(' ')[0]; // dd/MM/yyyy
 
     if (!users[user]) {
-      users[user] = { email: user, days: new Set(), events: 0, rawCmds: new Set(), gateCmds: [], versions: new Set() };
+      users[user] = { email: user, days: new Set(), events: 0, rawCmds: new Set(), gateCmds: [] };
     }
     const u = users[user];
     u.events++;
     if (date) u.days.add(date);
-    if (version.trim()) u.versions.add(version.trim());
 
     const cmd = norm(command);
     if (cmd) u.rawCmds.add(cmd);
@@ -151,19 +130,6 @@ const SCORE_LABELS = [
   'Sử dụng thường xuyên workflow',
 ];
 
-// ── Version status for a user ──────────────────────────────────────────────
-function getVersionStatus(u) {
-  const all = [...u.versions];
-  const parsed = all.map(v => ({ raw: v, parts: parseVersion(v) })).filter(v => v.parts);
-  if (parsed.length === 0) {
-    return { status: all.length ? 'unknown' : 'none', latest: null, all };
-  }
-  parsed.sort((a, b) => compareVersion(a.parts, b.parts));
-  const latest = parsed[parsed.length - 1];
-  const isOutdated = compareVersion(latest.parts, parseVersion(CURRENT_VERSION)) < 0;
-  return { status: isOutdated ? 'outdated' : 'ok', latest: latest.raw, all };
-}
-
 // ── Build summary row for each user ───────────────────────────────────────
 function buildRow(email, u) {
   const { events, days, rawCmds, gateCmds } = u;
@@ -232,7 +198,6 @@ function buildRow(email, u) {
     impactLabel: '',
     totalScore: score,
     notes,
-    versionStatus: getVersionStatus(u),
   };
 }
 
@@ -331,78 +296,11 @@ function writeExcel(rows, workbook, sheetLabel, fromLabel, toLabel) {
   return sheet;
 }
 
-// ── Version warning sheet ───────────────────────────────────────────────────
-function writeVersionSheet(workbook, rows) {
-  const sheet = workbook.addWorksheet('Version Warning');
-  sheet.columns = [
-    { key: 'no', width: 5 },
-    { key: 'email', width: 30 },
-    { key: 'status', width: 16 },
-    { key: 'latest', width: 16 },
-    { key: 'allVersions', width: 30 },
-    { key: 'note', width: 50 },
-  ];
-
-  const border = {
-    top: { style: 'thin' }, left: { style: 'thin' },
-    bottom: { style: 'thin' }, right: { style: 'thin' },
-  };
-
-  sheet.addRow([`Cảnh báo phiên bản — Yêu cầu phiên bản hiện tại: ${CURRENT_VERSION}`]);
-  sheet.mergeCells('A1:F1');
-  const title = sheet.getCell('A1');
-  title.font = { bold: true, size: 13, color: { argb: 'FF1F3864' } };
-  title.alignment = { vertical: 'middle', horizontal: 'center' };
-  title.fill = { type: 'pattern', pattern: 'solid', fgColor: { argb: 'FFD6DCE4' } };
-  sheet.getRow(1).height = 28;
-
-  const HEADERS = ['#', 'Email', 'Trạng thái', 'Phiên bản mới nhất', 'Các phiên bản dùng trong tuần', 'Ghi chú'];
-  const hRow = sheet.addRow(HEADERS);
-  hRow.height = 20;
-  hRow.eachCell(cell => {
-    cell.fill = { type: 'pattern', pattern: 'solid', fgColor: { argb: 'FF4F81BD' } };
-    cell.font = { bold: true, color: { argb: 'FFFFFFFF' }, size: 11 };
-    cell.alignment = { vertical: 'middle', horizontal: 'center', wrapText: true };
-    cell.border = border;
-  });
-
-  const warnings = rows.filter(row => row.versionStatus.status === 'outdated' || row.versionStatus.status === 'unknown');
-
-  const STATUS_LABEL = { outdated: 'CŨ HƠN', unknown: 'KHÔNG XÁC ĐỊNH', ok: 'OK', none: 'Không có dữ liệu' };
-  const STATUS_COLOR = { outdated: 'FFFFC7CE', unknown: 'FFFFEB9C' };
-
-  warnings.forEach((row, idx) => {
-    const vs = row.versionStatus;
-    const note = vs.status === 'outdated'
-      ? `Đang dùng ${vs.latest}, chưa cập nhật lên ${CURRENT_VERSION}`
-      : 'Không đọc được phiên bản (giá trị "-" hoặc "unknown") — cần kiểm tra lại';
-    const r = sheet.addRow([
-      idx + 1, row.email, STATUS_LABEL[vs.status], vs.latest || '-', vs.all.join(', ') || '-', note,
-    ]);
-    r.height = 20;
-    const fill = { type: 'pattern', pattern: 'solid', fgColor: { argb: STATUS_COLOR[vs.status] || 'FFFFFFFF' } };
-    r.eachCell({ includeEmpty: true }, (cell, col) => {
-      cell.border = border;
-      cell.fill = fill;
-      cell.alignment = (col <= 4)
-        ? { vertical: 'middle', horizontal: 'center' }
-        : { vertical: 'middle', horizontal: 'left', wrapText: false };
-    });
-  });
-
-  sheet.views = [{ state: 'frozen', ySplit: 2 }];
-  sheet.autoFilter = { from: 'A2', to: 'F2' };
-
-  return warnings;
-}
-
 async function writeExcelFile(rows, outputPath, sheetLabel, fromLabel, toLabel) {
   const workbook = new ExcelJS.Workbook();
   writeExcel(rows, workbook, sheetLabel, fromLabel, toLabel);
-  const warnings = writeVersionSheet(workbook, rows);
   await workbook.xlsx.writeFile(outputPath);
-  console.log(`Written: ${outputPath} (${rows.length} users, ${warnings.length} version warning(s))`);
-  return warnings;
+  console.log(`Written: ${outputPath} (${rows.length} users)`);
 }
 
 // ── Canonical user list (fixed order) ─────────────────────────────────────
@@ -437,7 +335,7 @@ const LOG_EMAIL_ALIAS = {
 };
 
 const EMPTY_USER = (email) => ({
-  email, events: 0, days: new Set(), rawCmds: new Set(), gateCmds: [], versions: new Set(),
+  email, events: 0, days: new Set(), rawCmds: new Set(), gateCmds: [],
 });
 
 // ── Main ───────────────────────────────────────────────────────────────────
@@ -471,7 +369,6 @@ const EMPTY_USER = (email) => ({
       u.events += data.events;
       data.days.forEach(d => u.days.add(d));
       data.rawCmds.forEach(c => u.rawCmds.add(c));
-      data.versions.forEach(v => u.versions.add(v));
       u.gateCmds.push(...data.gateCmds);
     }
   }
@@ -482,9 +379,5 @@ const EMPTY_USER = (email) => ({
     return buildRow(email, u);
   });
 
-  const warnings = await writeExcelFile(rows, outputFile, sheetLabel, fromLabel, toLabel);
-  if (warnings.length) {
-    console.log(`\n⚠️  Version warnings (< ${CURRENT_VERSION} or unknown):`);
-    warnings.forEach(w => console.log(`  - ${w.email}: ${w.versionStatus.latest || 'unknown'} (${w.versionStatus.status})`));
-  }
+  await writeExcelFile(rows, outputFile, sheetLabel, fromLabel, toLabel);
 })();

package/scripts/detect.js

@@ -85,6 +85,28 @@ class TaskDetector {
                 antiKeywords: ['code', 'fix', 'bug'],
                 icon: '📝',
                 description: 'Generate document from source code / feature analysis'
+            },
+            'create-system-requirement': {
+                keywords: [
+                    'system requirement', 'system requirements', 'srs',
+                    'bridge uc', 'translate uc', 'uc to system requirement',
+                    'uc spec to system', 'tạo system requirement',
+                    'system requirement từ uc', 'dịch uc spec'
+                ],
+                antiKeywords: ['bug', 'fix'],
+                icon: '📐',
+                description: 'Bridge UC Spec into a Dev-facing System Requirement'
+            },
+            'ingest-data': {
+                keywords: [
+                    'ingest', 'meeting minutes', 'meetings log', 'qna log',
+                    'confirmations log', 'tổng hợp buổi họp', 'biên bản họp',
+                    'tổng hợp feedback khách hàng', 'ingest data', 'ingest link',
+                    'ingest text', 'qna-log', 'meetings-log', 'confirmations-log'
+                ],
+                antiKeywords: ['code', 'bug', 'fix'],
+                icon: '📥',
+                description: 'Ingest a Backlog/Jira/SharePoint link or pasted text into AK-Docs/01.QnA/ logs'
             }
         };
     }

package/scripts/hooks/session-start.js

@@ -188,6 +188,7 @@ function inferWorkflow(ctx) {
     if (t === 'gen-doc') return 'gen-doc';
     if (t === 'testing') return 'create-testcase';
     if (t === 'spec') return 'create-spec';
+    if (t === 'create-system-requirement') return 'create-system-requirement';
     if (!t || ['feature', 'bug-fix', 'refactor', 'documentation', 'investigation'].includes(t)) return 'coding';
     return null;
 }

package/scripts/init.js

@@ -2,7 +2,7 @@ const fs = require('fs-extra');
 const path = require('path');
 const os = require('os');
 const chalk = require('chalk');
-const { input, checkbox, confirm } = require('@inquirer/prompts');
+const { input, checkbox, confirm, select } = require('@inquirer/prompts');
 const { syncDocsRepos } = require('./docs-repo');
 const memoryStore = require('./memory-store');
 
@@ -937,6 +937,29 @@ async function setupAdapter(projectDir, adapter) {
         console.log(chalk.green(`✓ Credentials verified successfully`));
     }
 
+    // Backlog: let the user pick a default project for tasks created manually (no ticket to
+    // derive one from otherwise) — kept for later use, e.g. syncing a local task up to Backlog.
+    if (adapter === 'backlog' && verifyResult.ok) {
+        const spaceKey = credentials.BACKLOG_SPACE_KEY;
+        const domain = spaceKey.includes('.') ? spaceKey : `${spaceKey}.backlog.com`;
+        try {
+            const { fetchBacklogProjects } = require('./use');
+            const projects = await fetchBacklogProjects(domain, credentials.BACKLOG_API_KEY);
+            if (projects.length > 0) {
+                const projectId = await select({
+                    message: 'Default Backlog project for tasks created manually (no ticket):',
+                    choices: projects.map((p) => ({ name: `${p.projectKey}  ${p.name}`, value: p.id })),
+                });
+                const picked = projects.find((p) => p.id === projectId);
+                credentials.BACKLOG_DEFAULT_PROJECT_ID = picked.id;
+                credentials.BACKLOG_DEFAULT_PROJECT_KEY = picked.projectKey;
+                console.log(chalk.green(`✓ Default project set to ${picked.projectKey}.`));
+            }
+        } catch (err) {
+            console.log(chalk.gray(`  (Could not fetch Backlog projects to pick a default: ${err.message} — skipping.)`));
+        }
+    }
+
     const claudeConfigDir = path.join(
         process.env.APPDATA ||
         (process.platform === 'darwin'