## /ak-ask — Ask a Question About ai-flow-kit Itself

**Why this command exists:** the `aiflow-help` skill normally triggers on keyword match or an `AKQ:` / `[AKQ]:` prefix, but that detection can be missed or ambiguous — especially when a question about ai-flow-kit's own usage (install, roles, folder structure, CLI, memory workflow) is phrased in a way that overlaps with real ticket work. `/ak-ask` is an explicit, unambiguous trigger: whatever follows is a self-help question about the kit, not the developer's current ticket.

**Question:** $ARGUMENTS

**Steps — do these now, in order:**

1. Do **not** treat this as ticket/coding work — do not touch `.aiflow/context/current.json` or start any Gate.
2. Read the topic index — `docs/common/INDEX.md` (inside the ai-flow-kit repo itself) or `.aiflow/docs/INDEX.md` (in a scaffolded project).
3. Match the question above against the "Ask about" table in that index, and read the linked doc file(s). Don't answer from memory of what ai-flow-kit "probably" does — CLI sub-commands and options change between versions (check `docs/common/CHANGELOG.md` if anything looks stale).
4. Answer directly and concisely, in whatever language the question was 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, run from the terminal) as a fallback. Never invent a command, flag, or file path you haven't actually read.

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