Prepare, verify, publish, and close an Engineering Board maintainer release. Use for repository maintenance when the owner asks to bump the product version, prepare a release, rebuild or pin the MCP bundle, update the changelog, create a release tag, publish to GitHub, PyPI, or the MCP Registry, or verify release…
Protocol for promoting sessions/ scratch entries to the live board on real session end. Triggers when the user says "consolidate the board", "promote scratch", "run consolidation", or when the Stop hook on a non-orchestrator session resolves at session end. Defense-in-depth — re-applies the imperative-verb blocklist…
Interpret a ranked Engineering Board cluster into an evidence-linked proposed root-cause hypothesis. Use for /board-insights, /board-hypothesis, /board-demo, and questions about shared causes. Never confirms causation.
This skill should be used when the user says "log this to the board", "route this finding", "add a bug", "create a board entry", "intake this", "new finding", "track this issue", "add an observation", or when a confirmed bug, regression, unexpected behavior, root cause, or noteworthy observation surfaces during a…
Use this skill when the user asks to close or resolve an entry. Also use it when the entry satisfies its completion criteria and verification is complete.
This skill should be used when the user asks "what's next", "what should I work on", "triage the board", "what's the priority", "what order should I fix these", "start work on", "begin implementation", "pick up the next item", or wants a recommended sequence derived from the current open items.