---
name: aiflow-help
description: Answers questions about ai-flow-kit itself (install, roles, folder structure, CLI commands, memory draft/submit, troubleshooting) — trigger on install/setup/how-do-I-use-this/roles/folder-structure/memory-submit questions or an AKQ:/[AKQ]: prefix, even with no active ticket; skip for actual coding/ticket work. Read docs/common/INDEX.md first, cite the file used, and say plainly if a topic isn't documented instead of guessing.
keywords: aiflow, ai-flow-kit, ak, install, cai dat, huong dan, PM, role, folder structure, thu muc, memory, submit memory, cli, commands, AKQ, how to use, huong dan su dung
---

# AI Flow Kit — Self-Help

Answers questions **about ai-flow-kit itself** — not about the ticket/feature the developer is currently building. Examples: "how do I install this", "I'm a PM, how do I use ai kit", "give me an overview of the folder flow", "how do I manually create and submit a memory".

## When this applies

- The message is prefixed with `AKQ:` or `[AKQ]:` — always treat it as a self-help question, whatever else it contains.
- Or the message asks about install/setup, roles (PM/DEV/AI), folder/`AK-Docs` structure, CLI commands, the `99.Memory/` workflow, switching between Claude Code/Cursor/Gemini, or troubleshooting — **even when there is no active ticket** in `.aiflow/context/current.json`.
- Does **not** apply to requests to analyze, implement, fix, or review an actual ticket/feature — that's the Gate Workflow's job, not this skill's.

## What to do

1. Do **not** auto-start Gate 1 for this turn — this is a support question, not a coding task.
2. Read `docs/common/INDEX.md` (in a scaffolded project this is copied to `.aiflow/docs/INDEX.md`; inside the ai-flow-kit repo itself it's `docs/common/INDEX.md`).
3. Match the question against the "Ask about" table and read the linked doc file(s) — don't answer from memory of what ai-flow-kit "probably" does; the CLI's actual sub-commands and options change between versions (check `CHANGELOG.md` if anything looks stale).
4. Answer directly and concisely, in whatever language the user asked in. Cite the file path you read from (e.g. "per `docs/common/cli-reference.md`").
5. If the topic is listed under INDEX.md's "Unanswered topics", or isn't covered anywhere: say plainly it isn't documented yet, point to the closest related doc, and suggest `ak guide` (quickstart + command reference) or `ak ask "<question>"` (local keyword search across the docs) as a fallback. Never invent a command, flag, or file path that you haven't actually read.

## After answering

Stay in this mode for follow-up questions in the same vein. Only return to the normal Gate Workflow once the developer starts talking about an actual ticket/feature again.