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

package/custom/rules/project-conventions.md

@@ -1,51 +1,67 @@
-# Project Conventions (Override Skill Defaults)
-
-> **MANDATORY:** These rules override ANY upstream skill default (including `writing-plans`, `generate-spec`, and all superpowers skills).
-> Read this file before writing any output file during the Gate Workflow.
-
----
-
-## Plan Output Paths
-
-| Output | Path | Note |
-|--------|------|------|
-| Requirement doc | `plan/[ticket-id]/requirement.md` | Gate 1 output |
-| Implementation plan | `plan/[ticket-id]/plan.md` | Gate 2 output — **NOT** `docs/superpowers/plans/` |
-| Summary | `plan/[ticket-id]/summary.md` | Gate 4 output |
-
-> **Override:** The `writing-plans` skill defaults to `docs/superpowers/plans/<filename>.md`.
-> In this project, **always save plans to `plan/[ticket-id]/plan.md` instead.**
->
-> The `[ticket-id]` comes from `.aiflow/context/current.json`.
-> If no ticket context exists, use a descriptive slug: `plan/<feature-name>/plan.md`.
-
----
-
-## Execution Handoff Message
-
-When `writing-plans` skill says to announce the saved path, use the **actual path**:
-
-```
-Plan complete and saved to `plan/[ticket-id]/plan.md`. Two execution options: ...
-```
-
-Do NOT copy the hardcoded path from the skill template (`docs/superpowers/plans/`).
-
----
-
-## Checklist Before Writing Any File
-
-Before saving any plan, requirement, or summary file, verify:
-
-- [ ] Output path follows the table above — NOT the skill's default path
-- [ ] `[ticket-id]` is read from `.aiflow/context/current.json`
-- [ ] Directory `plan/[ticket-id]/` exists or will be created
-- [ ] Announced path in the handoff message matches the actual saved path
-
----
-
-## Other Conventions
-
-- **Review checklist:** `custom/rules/review-checklist.md`
-- **Code style:** `custom/rules/code-style.md`
-- **Naming:** `custom/rules/naming.md`
+# Project Conventions (Override Skill Defaults)
+
+> **MANDATORY:** These rules override ANY upstream skill default (including `writing-plans`, `generate-spec`, and all superpowers skills).
+> Read this file before writing any output file during the Gate Workflow.
+
+---
+
+## DEV Workflow Output Paths (`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` |
+
+> **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.**
+
+### 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.
+  - 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.
+
+### Legacy
+
+- ❌ Đường dẫn cũ `plan/[ticket-id]/requirement.md`, `plan/[ticket-id]/plan.md`, `plan/[ticket-id]/summary.md` đã **DEPRECATED** — không được ghi output mới vào `plan/`.
+
+---
+
+## Execution Handoff Message
+
+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: ...
+```
+
+Do NOT copy the hardcoded path from the skill template (`docs/superpowers/plans/`).
+
+---
+
+## Checklist Before Writing Any File
+
+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
+- [ ] Announced path in the handoff message matches the actual saved path
+
+---
+
+## Other Conventions
+
+- **Review checklist:** `custom/rules/review-checklist.md`
+- **Code style:** `custom/rules/code-style.md`
+- **Naming:** `custom/rules/naming.md`
+- **Folder structure reference:** `docs/internal/Coding-Structure.md` · `docs/internal/Project-Structure.md`

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. `plan/[ticket-id]/requirement.md`, `plan/[ticket-id]/plan.md`, or `docs/ak-[project]/...`) as specified by the gate instructions.
+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.
 
 ### Step 3: Display gate pause message
 

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

@@ -1,99 +1,99 @@
----
-name: generate-spec
-description: Gate 2 — After DEV approves the requirement document (Gate 1), AI creates a detailed implementation plan using TDD approach. This is the bridge between requirement and code.
-keywords: spec, plan, implementation, tdd, coding plan
----
-
-# Implementation Plan — Gate 2
-
-> **GATE 2: Runs after Gate 1 (requirement document) has been APPROVED by DEV.**
->
-> Principle: AI uses the approved requirement document to create a detailed implementation plan with TDD steps. DEV confirms the plan before coding begins.
-
----
-
-## Conditions to Enter Gate 2
-
-- ✅ Gate 1 APPROVED — `plan/[ticket-id]/requirement.md` reviewed and approved by DEV
-- ✅ Requirement document includes: requirements, solution, impact analysis, estimate
-
-## Fast Mode Output Rules (CRITICAL)
-
-When updating `plan/[ticket-id]/summary.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.**
-
----
-
-## Process
-
-### Step 1: Read Approved Requirement
-
-Read `plan/[ticket-id]/requirement.md` — use the chosen approach, file list, and testing plan as input.
-
-### Step 2: Create Implementation Plan
-
-**INVOKE:** `superpowers:writing-plans`
-
-Create a detailed step-by-step plan based on the requirement document:
-
-```markdown
-## Implementation Plan
-
-### Task Breakdown (TDD Order)
-
-| # | Task | File | Test First? | Dependencies |
-|---|------|------|-------------|--------------|
-| 1 | Write test for [scenario] | [test file] | ✅ | None |
-| 2 | Implement [component] | [source file] | — | Task 1 |
-| 3 | Write test for [scenario] | [test file] | ✅ | Task 2 |
-| ... | ... | ... | ... | ... |
-
-### Test Commands
-```bash
-[specific test commands for this project]
-```
-```
-
-### Step 3: GATE 2 — Present Plan & Start Coding
-
-```markdown
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-⏸️  GATE 2: IMPLEMENTATION PLAN READY
-
-Based on the approved requirement document, here is the coding plan:
-
-[Show task breakdown summary]
-
-**Total tasks:** [N]
-**Test-first tasks:** [N]
-
-Ready to start coding?
-Type **"APPROVED"** to begin implementation.
-Type feedback to adjust the plan.
-
-⚠️  I will NOT write code until I receive "APPROVED".
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### Step 4: Handle Feedback
-
-**If DEV provides feedback:**
-→ Update the implementation plan
-→ Re-display GATE 2 prompt
-
-**If DEV types "APPROVED":**
-→ Proceed to Gate 3 (Code Generation with TDD)
-→ Follow the task breakdown order exactly
-
----
-
-## Mandatory Rules
-
-- ❌ **DO NOT** start coding until "APPROVED" is received for the plan
-- ❌ **DO NOT** deviate from the approved requirement document
-- ✅ **MUST** use TDD order: test first, then implementation
-- ✅ **MUST** invoke `superpowers:writing-plans` for plan creation
-- ✅ **MUST** show clear task breakdown before getting approval
-- ❌ **DO NOT** include `git commit`, `git add`, or any git operations in the plan. The developer manages commits manually.
+---
+name: generate-spec
+description: Gate 2 — After DEV approves the requirement document (Gate 1), AI creates a detailed implementation plan using TDD approach. This is the bridge between requirement and code.
+keywords: spec, plan, implementation, tdd, coding plan
+---
+
+# Implementation Plan — Gate 2
+
+> **GATE 2: Runs after Gate 1 (requirement document) has been APPROVED by DEV.**
+>
+> Principle: AI uses the approved requirement document to create a detailed implementation plan with TDD steps. DEV confirms the plan before coding begins.
+
+---
+
+## Conditions to Enter Gate 2
+
+- ✅ Gate 1 APPROVED — `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**:
+- **Keep it extremely short.**
+- Add a bullet point indicating Gate 2 plan is ready.
+- **DO NOT copy the entire plan.md into summary.md.**
+
+---
+
+## Process
+
+### Step 1: Read Approved Requirement
+
+Read `04.Coding/01.Requirements/[functionId]/[ticketId].md` — use the chosen approach, file list, and testing plan as input.
+
+### Step 2: Create Implementation Plan
+
+**INVOKE:** `superpowers:writing-plans`
+
+Create a detailed step-by-step plan based on the requirement document:
+
+```markdown
+## Implementation Plan
+
+### Task Breakdown (TDD Order)
+
+| # | Task | File | Test First? | Dependencies |
+|---|------|------|-------------|--------------|
+| 1 | Write test for [scenario] | [test file] | ✅ | None |
+| 2 | Implement [component] | [source file] | — | Task 1 |
+| 3 | Write test for [scenario] | [test file] | ✅ | Task 2 |
+| ... | ... | ... | ... | ... |
+
+### Test Commands
+```bash
+[specific test commands for this project]
+```
+```
+
+### Step 3: GATE 2 — Present Plan & Start Coding
+
+```markdown
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⏸️  GATE 2: IMPLEMENTATION PLAN READY
+
+Based on the approved requirement document, here is the coding plan:
+
+[Show task breakdown summary]
+
+**Total tasks:** [N]
+**Test-first tasks:** [N]
+
+Ready to start coding?
+Type **"APPROVED"** to begin implementation.
+Type feedback to adjust the plan.
+
+⚠️  I will NOT write code until I receive "APPROVED".
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+### Step 4: Handle Feedback
+
+**If DEV provides feedback:**
+→ Update the implementation plan
+→ Re-display GATE 2 prompt
+
+**If DEV types "APPROVED":**
+→ Proceed to Gate 3 (Code Generation with TDD)
+→ Follow the task breakdown order exactly
+
+---
+
+## Mandatory Rules
+
+- ❌ **DO NOT** start coding until "APPROVED" is received for the plan
+- ❌ **DO NOT** deviate from the approved requirement document
+- ✅ **MUST** use TDD order: test first, then implementation
+- ✅ **MUST** invoke `superpowers:writing-plans` for plan creation
+- ✅ **MUST** show clear task breakdown before getting approval
+- ❌ **DO NOT** include `git commit`, `git add`, or any git operations in the plan. The developer manages commits manually.

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

@@ -30,11 +30,13 @@ Check `mode` in `.aiflow/context/current.json` before starting:
 
 ## Fast Mode Output Rules (CRITICAL)
 
-When creating `plan/[ticket-id]/summary.md` during Gate 1:
+When creating `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.
 
+> **Path variables:** `[functionId]` (mã chức năng do dự án quy định, ví dụ `F-001_User-Login`, `AD06`) và `[ticketId]` (= `taskId` trong `.aiflow/context/current.json`) được xác định ở **Gate 1 Pre-flight Bước 0** của workflow — ưu tiên lấy từ context, sau đó suy từ file UC Spec input (nội dung/đường dẫn) rồi hỏi DEV xác nhận. KHÔNG ghi bất kỳ file output nào khi chưa có functionId.
+
 0. **Pre-flight — Sync with remote** (before reading any source file):
    - Run `git status --porcelain` to check for uncommitted changes.
    - Working tree clean → run `git pull --ff-only` to fetch the latest code.
@@ -46,7 +48,7 @@ When creating `plan/[ticket-id]/summary.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 `plan/[ticket-id]/requirement.md` with **3 sections only**:
+4. Output `04.Coding/01.Requirements/[functionId]/[ticketId].md` with **3 sections only**:
 
 ```markdown
 # Requirement: [Ticket ID] — [Title]
@@ -152,7 +154,7 @@ After the developer confirms the design direction (Step 2), extend with:
 
 ### Step 4: Write Requirement Document
 
-Save to `plan/[ticket-id]/requirement.md`:
+Save to `04.Coding/01.Requirements/[functionId]/[ticketId].md`:
 
 ```markdown
 # Requirement: [Ticket ID] — [Title]
@@ -282,7 +284,7 @@ Save to `plan/[ticket-id]/requirement.md`:
 ⏸️  GATE 1: REQUIREMENT DOCUMENT READY
 
 Ticket: [ticket-id] — [title]
-File:   plan/[ticket-id]/requirement.md
+File:   04.Coding/01.Requirements/[functionId]/[ticketId].md
 
 Summary:
   Type:     [feature / bug-fix / refactor]
@@ -330,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 `plan/[ticket-id]/requirement.md`
+- ✅ **MUST** save `04.Coding/01.Requirements/[functionId]/[ticketId].md`
 - ✅ **MUST** display Gate 1 prompt and wait for `APPROVED`