middle

Use when the user wants to file GitHub issues from a planning document, build spec, brainstorm output, or any structured source. Triggers include "create issues for this spec", "file these as issues", "seed this project on GitHub", "break this plan into issues". Drives issue creation only — sets titles, bodies, acceptance criteria, labels, and parent/sub-issue hierarchy. Does NOT implement, does NOT open PRs, does NOT pick what to work on next.

Use when the user provides a GitHub issue number or URL and asks to implement it end-to-end. Triggers include "implement issue

Use when running as the dispatch recommender for a single GitHub repo. Triggers when invoked by middle-management with a state issue number and rate-limit context. The recommender's sole job is to rewrite the state issue body with a ranked dispatch plan and a needs-human digest, conforming to the agent-queue state issue schema. NEVER writes code, NEVER modifies non-state issues, NEVER opens PRs. If asked for anything other than a recommender run, decline and state this skill is recommender-only.

Use when filing or auditing GitHub issues to check their acceptance criteria demand integration into the running product, not just green unit tests. Defines the integration rubric and drives `mm audit-issues`. Triggers include "audit these issues", "do the acceptance criteria hold up", "harden this issue's requirements", and the second pass inside creating-github-issues. Suggests rewrites; does NOT implement, does NOT silently edit issues.

Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts.

Use when writing or revising any documentation in this repo — README, docs/ guides, TSDoc on public exports, module-index frontmatter, per-folder CLAUDE.md, or prose the Docs-harvester bot generates. Enforces Diátaxis (every doc is exactly one of tutorial / how-to / reference / explanation), the repo's voice (Google + Microsoft style guides), an LLM-ism blocklist, and the accuracy rule that code samples come from working source. Triggers include "write docs for X", "document this package", "audit the docs", "fix the README", "add a how-to". Authoring + audit only — does NOT change code behavior, does NOT open PRs.