summonerlisted

# Summoner — AI Agent Orchestration Framework ## Overview Summoner is the routing hub. It reads the project's `summoner.yaml` manifest, resolves phase names to domain skills, enforces checkpoint pauses between phases, and triggers post-game review at workflow end. It does NOT implement any domain logic itself — that lives in project skills. ## When to Use - User invokes `/summoner:fix`, `/summoner:new`, `/summoner:ship`, `/summoner:debug`, `/summoner:ops`, `/summoner:review`, or `/summoner:release` - User expresses intent that matches a Summoner workflow (e.g., "帮我排查这个线上 bug" → suggest `/summoner:fix`) **When NOT to use:** - User explicitly says "直接用 my-debug-skill" or names a specific domain skill → route directly, skip Summoner orchestration - Pure Q&A, no workflow needed → respond directly ## Core Operating Behaviors ### 0. Memory Retrieval (Phase 0) Before starting any workflow, check Summoner Memory for relevant historical patterns. 1. Read `project.name` from the project's `summoner.yaml` 2. Check if memory database exists: `memory/{project-name}.db` (under Summoner plugin root — the installed plugin dir, resolved via `${CLAUDE_PLUGIN_ROOT}` in Claude Code; the actual path is typically `~/.claude/plugins/cache/summoner-marketplace/summoner/<version>/memory/`) - If not: run `${CLAUDE_PLUGIN_ROOT}/scripts/init-memory-db.sh {project-name}` to create and seed it (in Claude Code). On other platforms, locate the installed plugin dir (contains `scripts/` + `memory/