specialist-profileslisted

# specialist-profiles — legacy four-stage agents ## Stage-parent model GPT-5.6 Luna is the overall coordinator and may dispatch Opus 5/Claude Code for planning after decisions are known. Kimi K3/Pi, GPT-5.6 Luna/Codex, and Grok 4.5/Pi are independent top-level parent sessions for coder, debugger, and reviewer. Each stage parent may coordinate one level of helpers; a native child may not spawn nested children. The default profile is Opus 5/Claude Code for planner, Kimi K3/Pi via OpenRouter for coder, GPT-5.6 Luna/Codex at max effort for debugger, and Grok 4.5/Pi via OpenRouter for reviewer. The stage boundary is carried by the GitHub Project item, GitHub issue/PR artifacts, and handoffs. Keep the stages serial and preserve a fresh reviewer context. Role separation exists for one reason: **a single context that plans, builds, and reviews its own work will accept its own work.** Separation makes maker≠checker structural instead of aspirational. ## The four roles Defined in this installation as stage-parent roles under `~/.claude/agents/` or the corresponding top-level harness sessions: | Agent | Queue | Entry skills | May move | |---|---|---|---| | `legacy-planner` | Planned | `github-projects-pipeline` → `legacy-planner` (+ `batch-grill-me`) | creates GitHub issues in Planned; promotes unblocked project items to Agent Ready | | `legacy-coder` | Agent Ready (incl. scope/test bounce returns) | `github-projects-pipeline` → `legacy-coder` (+ `ticket-implementation-tdd`) | Ag