Resume Context
Use at the start or resume of any task (especially long or multi-session tasks) to load the lessonbook before acting — read the read-only control rules and approved lessons plus the task's working state, and surface the active constraints for this run. Use when starting/resuming work, picking up a long task, or when continuity across sessions matters. Do not use for one-shot factual lookups with…
Groundcheck
Use when the user wants to fact-check, verify, or ground existing content — checking generated text, an answer, a report, RAG output, documentation, or code for fabricated or unsupported claims. Triggers on requests like "verify these claims", "check for hallucinations", "are these citations / numbers / APIs real", "fact-check this before I publish", or "is this actually supported by the source".…
Deliberative Analysis
Use when comparing non-trivial options or making a design/architecture/experiment/product/research/strategy decision with real tradeoffs, unclear criteria, or commitment risk, and the user says things like "比较一下 A 和 B", "还有别的方案吗", "方案的利弊/权衡是什么", "这样设计好不好", "换个角度", "深入分析", "review my plan", "compare A vs B vs A+B", "what are the alternatives", "what are the tradeoffs", "is this the right approach"…
Correction Capture
Use the moment evidence appears that should influence FUTURE execution and would be wrong for the worker to treat as authority on its own — a user correction/clarification ("actually…", "you skipped X again"), exposed drift (a check fails, a miss is pointed out), a proven repo pitfall, a "never do X" constraint, or an authority-relevant architecture constraint. Record it to the task's correction…
Goal Compile
Use when the user sets a substantial, multi-step or long-running goal/task — naturally phrased, no prefix needed: "设计goal: ...", "goal: ...", "我的目标是...", "帮我完成这个任务/目标", "help me build/implement X", "做一个X". For work that produces a user-visible artifact (feature, page, report, export, copy/文案, schema, release, migration, experiment) — short length does not exempt it — or spans multiple files/steps…
Grill All
Use when stress-testing a coding plan or design and the right answers may come from the human, project docs, codebase, or the web.
Shipping Skills
Use when the user wants to package, publish, ship, or distribute an Agent Skill to GitHub — structuring the repo, getting the frontmatter spec-compliant, naming for discoverability, releasing with tags, pre-publish review, and getting it listed (skills.sh, directories). Complements an authoring/skill-creator skill (which writes the SKILL.md body); this takes a ready skill to a discoverable, publi…
Agent Arena
Use when the user asks for a second opinion, independent/heterogeneous review, architecture red-team, cross-model critique (Codex/Claude/GLM/DeepSeek/Qwen/Kimi), review my plan, challenge this design, evidence-checked code/PR review, or multi-agent critique of a high-stakes plan, design, research claim, or bug root-cause. Not for simple lookups, formatting, or low-stakes tasks. On error_max_turns…
Completion Audit
Use before declaring a long, multi-stage, or artifact-producing task done — prepare a completion CANDIDATE (not a completion). Enumerate touched user-visible surfaces, reconcile thread expectations against the plan, gather real evidence paths, and run the external gate; any uncovered surface, failed check, or review item forces blocked. Use at task wrap-up for long/high-stakes work. Do not use to…
Completion Gate Init
Use when the user asks to set up / install / initialize the completion gate in their project (e.g. "set up the completion gate", "add the completion gate to this repo"). Runs the bundled deterministic scaffolder (scripts/init.sh) to create gate/, control/, state/, and a CI workflow, then tells the user what THEY must protect. Does NOT make the gate authoritative — branch protection + CODEOWNERS a…
Lesson Propose
Use at task wrap-up, after a mistake, or on a postmortem to turn the correction journal and observations into review PROPOSALS — classify each candidate lesson by target tier (working-only / approved-lesson / policy / gate-candidate) and write a proposal note, without self-approving. Use when wrapping up, after something went wrong, or when a correction should persist. Do not grant a lesson autho…