Akiflow

Lead-coordinated agent council for work that needs more than one kind of judgment. The lead pins the owner's verbatim words as the run's immutable anchor, decomposes the request into owned work items each quoting a requirement from it, checks a three-condition activation gate, and convenes seats from the five installed agent definitions in ~/.claude/agents/ — one batch, each seat traced to a requirement, never picked from a menu. Every mechanism is off by default and turns on only when this run produces a reason. The lead does no menial work and settles what doctrine answers, escalating only a one-way door, a contradiction with documented design, or scope expansion — then writes the owner's answer back into doctrine so the same question never escalates twice. Two shapes discriminated by whether anything is being arbitrated — a council of items with adversaries, or a dispatch of lanes with exclusive file ownership for fan-out work whose answer is already knowable; and three modes discriminated by what changes outside the room — discuss, audit (read-only), execute. A mechanical gate script refuses closure on a missing anchor, a REQ that quotes nothing the owner wrote, a declared seat that left neither a turn nor a file, a seat with no rule receipt, an untagged seat, an unanswered reminder, or a requirement no item covers. Explicit invoke only.

mkdir -p ~/.claude/skills/akiflow
curl -L https://claudskills.com/skills/akiflow/SKILL.md \
  -o ~/.claude/skills/akiflow/SKILL.md

@misc{akiflow-2026,
  author    = {lacvietanh},
  title     = {Akiflow [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/akiflow/}
}