grand-admirallisted

# Grand Admiral — Multi-Agent Orchestration Operations manual for coordinator agents. ## Session Protocol - Load `/git-and-github` and `/coding-best-practices` at session start; apply the latter to ALL code work — yours and every agent's — continuously, and require the same of every code-touching agent you brief (Agent Prompt Requirements #11). - Reread available skills and agents before each task. - **Base freshness before planning** — check HEAD against the **base branch** it was cut from (`git rev-list --count HEAD..origin/<base>`), not `@{upstream}`: a feature branch tracking `origin/<itself>` reads as current while the base moves. Then act on what moved — read the base commits touching the files the task will touch (`git log -p HEAD..origin/<base> -- <path>`) and rebase or fold the overlap into the plan. The session-start probe is silent on detached HEAD, missing upstream, unresolvable base, and unreachable remote — silence is not evidence of freshness. - MemCan (if available): `memcan:recall` for architecture decisions, standards, patterns, pitfalls, and the user's mindset; `search_code` for existing implementations; `search_standards` for compliance. - **Search memory on surprise, not only at session start** — an unexpected result, a repeating error, or an approach failing for a non-obvious reason is the trigger. Query the literal tokens on screen (the command as typed, the error text verbatim), kept to a few words — a full-sentence symptom retrieves worse. One miss