vulyk: Command for Claude Code

Enter Queen mode for: "$ARGUMENTS"

1. Classify the tier per the routing matrix in CLAUDE.md. Announce it. Tier 0-1: skip ceremony - say so and either do it (Tier 0) or write a single story and stop for approval (Tier 1). The ceremony floor: brief.md and ## Requirements quotes exist at Tier 2+; trace-check runs whenever stories exist; Tier 0-1 gets none of it.
2. Brief. Write docs/specs/<slug>/brief.md: the request VERBATIM as a > blockquote - the user's words, not your restatement - piped through bash scripts/redact.sh (briefs are committed; secrets are not), with the date. Everything downstream traces back to this file; a paraphrase here poisons every gate built on it. A bug report is a spec too: the error text, the stack trace and the reproduction go in verbatim, and the ask is the observable that must hold afterwards.
3. Briefing questions. Before asking the human anything, look it up - the repo, memory/, the brief itself answer most questions. Ask only what is irreversible, costly, a vendor choice, or a business rule no code can reveal. One question at a time, each with a recommended default so silence has a safe meaning. Append answers to brief.md under ## Answers (also verbatim). Then confirm the spec (stage 01). Show the brief back - the quote and the answers, nothing else - and at Tier 3-4 stop for one word before spending recon: every gate downstream answers to this text, and a wrong word here is built correctly by everything below it. At Tier 2 show it and continue unless corrected; silence means the text stands.
4. Recon, not reading. Check memory/memory.md and relevant memory/map/ slices first. Dispatch drone-scout (parallel, up to 4) only for territory the map does not cover or marks stale. You do not open source files yourself.
5. Plan. For Tier 2: draft the plan inline. For Tier 3-4: delegate synthesis to queen-planner with the brief, scout reports and map pointers attached; for Tier 4 also request a lead-architect consult on the central design fork before stories are finalized. Both dispatches carry model: <TOP_MODEL> - the alias the session brief announced (fable where the plan carries Fable 5.1, opus otherwise; bash scripts/top-model.sh if the brief scrolled away). The agent files say opus as the floor; the per-invocation parameter is where the plan-aware upgrade happens, and forgetting it plans on the floor. Plan file follows templates/plan.md - contracts between concurrent stories are decided here, in the one context that has seen the whole plan.
6. Stories. Ensure docs/specs/<slug>/ contains plan.md plus one story file per unit of work (template: templates/story.md). Each story: verbatim ## Requirements quotes from brief.md, files to touch, acceptance criteria, verification command, map slice pointer, model tier of its worker, and its wave:/blocked_by: lines. Wave rule: stories in one wave run concurrently, so their ## Files must be disjoint - when two stories need the same file, either merge them, move the shared file into its own earlier story, or push one to a later wave via blocked_by.
7. Check the stories, deterministically. Run bash scripts/wave-check.sh docs/specs/<slug> and bash scripts/trace-check.sh docs/specs/<slug> - both deterministic, both free. Wave-check catches the collision that would silently eat a worker's diff mid-build, the declared path that does not exist in the tree, and the story whose verification command cannot turn red for its own files; trace-check catches the story nobody asked for and the requirement no story carries. Fix findings in the story files now; a plan approved with either defect ships it.
8. Coverage, from outside the plan. Dispatch drone-coverage with exactly two paths: the brief and plan.md. It never sees the story files - that is the whole mechanism, because a check that reads the planner's own output cannot be independent of it. Its report is evidence, not authority: an absent or partial ask is either a story you owe or a line the human will call context. Do not resolve that yourself.
9. Stop for approval. Present: tier, story list with one-line summaries grouped by wave, open assumptions (Law 1), estimated token posture (how many worker dispatches, where top-model tokens will be spent), and all three verdicts - wave-check, trace-check and coverage - including which brief lines no story covers, because deciding "that line is context, not a requirement" belongs to the human, not the planner. Do NOT proceed to implementation - that is /vulyk-build, run after human approval. When it comes, replace the **Approved:** placeholder in plan.md with the owner and the date - that line is stage 02's confirmation, and it is the one /vulyk-build reads.