MrBinnacle

Closure-mode discipline at workflow boundaries. Use when a sprint, phase, or vertical slice locks clean, or when a multi-candidate "what next" decision arises. Owns the closure→build transition.

Decide whether a capability should become a skill. Use when asking "should this be a skill?", pruning a library, choosing skill vs CLAUDE.md vs MCP vs hook, or before building an eval instrument.

Use when dispatching parallel agents to verify/adjudicate findings — adversarial verify, security disposition, design triage, council fires. Shared disposition schema so seat outputs join cleanly.

Use before `git pull` where `pull.rebase` may be `true`. `--no-ff` does NOT stop a rebase under `pull.rebase=true` (silently ignored); it rewrites every local commit SHA. Check config first.

Framing discipline for any artifact instructing a downstream reader — handoffs, plans, ADRs, subagent prompts. Bans blanket do-not-re-litigate framing; requires per-decision Revisit-if clauses.

Reliability checks for web-research subagents. Pre-dispatch, verify the agent's tool grant actually includes web tools (else it no-ops or fabricates). Post-return, verify every citation before acting.

Verify a GitHub Pages (or any CDN-fronted) deploy actually serves new content. Poll on a marker that did not exist pre-deploy; avoid sleep-and-curl chains the agent harness blocks.

Decision-quality pre-commitment analysis for initiative-level go/no-go calls with meaningful downside and limited reversibility — launches, rewrites, key hires, partnerships, strategic bets, timelines. Invoke when the user explicitly asks to pressure test, validate, or evaluate such a decision (e.g. 'should we do this,' 'pressure test,' 'go/no-go,' 'are we ready'). Do NOT invoke for routine code review, sub-task planning, reversible tactical choices, or pure ideation.

Audits AZIMUTH's coverage completeness. Cross-references what SKILL.md claims to handle against what reference, diagnostic, and domain-policy files actually cover. Identifies thin coverage, missing domains, and structural inconsistencies. Run before major version planning.

Authoring discipline for new AZIMUTH reference files and templates. Use when adding a new domain reference file, extending an existing one, or creating a new template. Covers: (1) EXTEND vs. CREATE decision heuristic, (2) the Module 7 vocabulary header pattern that prevents domain-gap recurrence, (3) the sourcing caveat pattern for narrow-evidence-base files, (4) pre-verdict gate structure for templates. Validated by research-mpbaese4 (2026-05-18).

Tracks AZIMUTH's 8 primary citation source families for new publications or significant updates. Stages validated findings in research/staged-findings.md for human review before promotion to references/base-rates.md. Invoke with 'run the research scout' or 'promote staged findings'.

Stress-tests an AZIMUTH output against the skill's own structural rules. Paste an AZIMUTH output and invoke to get a severity-rated diagnostic. Diagnoses only — does not rewrite. Use after any real AZIMUTH session to detect quality drift.