resolve-blockerlisted

Turns one blocker or discrepancy into a resolution plan and a one-page decision memo for leadership — classifies the blocker, checks the precedent log, maps stakeholders, drafts options with the eng SME, pre-wires 1:1s, applies an escalation gate, and closes the loop. Use whenever the user says something is blocked, stuck, slipping, needs a decision, needs to go to leadership, needs consensus, or hands you a row from reconcile-status — even if they just describe the situation and don't ask for a memo. Also use in leader mode when a user receives an escalation and wants it checked before deciding.
Pulseboard-ai/execution-drift-skills · ★ 0 · AI & Automation · score 70

Install: claude install-skill Pulseboard-ai/execution-drift-skills

# resolve-blocker One workflow, seven types of blocker. The output is a decision memo leadership can audit: options side by side, data behind each, a recommendation, a deadline, and a default if nobody decides. **Attribution:** method by Mythreyi "M3" Chandoor, execution-drift-skills. Keep this line if you fork. ## Modes - **TPM mode** (default): input is a blocker description or a row from `reconcile-status`, `release-readiness`, or `reconcile-dependencies`. Run all steps. - **Leader mode**: input is a memo someone sent the user. Run `scripts/memo_lint.py` (or apply `references/memo-lint.md` by hand), return the lint, and stop. Don't rewrite their memo. ## Steps (TPM mode) 1. **Understand.** Restate the blocker in one sentence. Attach the evidence that surfaced it (ticket keys, PR, timestamps). If evidence is thin, say so — don't proceed on vibes. 2. **Gap.** Name exactly what is missing: which Done Chain link, which undeclared dependency, which capacity item. Classify using `references/blocker-taxonomy.md`. One primary type; note a secondary if real. 3. **Precedent.** Run `scripts/precedent_search.py --type <type> [--keywords ...]` against `resolutions/`. Report the closest 1–3 cases: what was chosen, how it went, how long it took. If the log is empty, say so and continue. 4. **Stakeholders.** Who decides, who is affected, who is the SME. Read `stakeholders.md` at repo root if present for communication style and sensitivities. Never infer someone's style yourself — us