assumption-audit

Resolve decision-shaped blocking gaps in active protocols through structured questioning.

16|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/sbluemin/fleet-harness --skill assumption-audit-sbluemin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assumption-audit
Source: https://github.com/sbluemin/fleet-harness/tree/main/packages/fleet-admiral/assets/skills/assumption-audit
Command: npx skills add https://github.com/sbluemin/fleet-harness --skill assumption-audit-sbluemin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses decision-shaped blocking gaps, providing a structured approach to resolve ambiguities during active protocols or pre-engagement requirements.

Core Features & Use Cases

  • Triage Blocking Gaps: Classify gaps as Scout-shaped, Decision-shaped, or Escalation-shaped, and handle them accordingly.
  • Decision-shaped Questions: Ask precise questions, offering recommended answers and alternatives.
  • Protocol Integrity: Ensures active workflows re-evaluate confidence and re-apply planning boundary gates after resolving gaps.
  • Use Case: When encountering a pre-engagement requirements ambiguity, use this Skill to ask a focused question, receive a response, and maintain protocol integrity.

Quick Start

Use the assumption-audit skill to resolve a decision-shaped blocking gap during an active protocol.

Frequently Asked Questions about assumption-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve decision-shaped blocking gaps in active protocols?

Decision-shaped blocking gaps are resolved by applying structured questioning, classifying the gap type, and offering recommended answers with alternatives to unblock the protocol.

What is the difference between Scout-shaped, Decision-shaped, and Escalation-shaped gaps?

Triage classifies blocking gaps into Scout-shaped, Decision-shaped, or Escalation-shaped categories, routing each to the appropriate resolution strategy based on the gap's nature.

How do I maintain protocol integrity after resolving a pre-engagement requirements ambiguity?

Protocol integrity is maintained by re-evaluating confidence levels and re-applying planning boundary gates after resolving the blocking gap to ensure workflow stability.

Can I use structured questioning to resolve ambiguities during pre-engagement requirements?

Yes, structured questioning targets pre-engagement ambiguities by asking focused questions, receiving responses, and maintaining protocol integrity throughout the resolution process.

What's the best way to handle decision shaping when a protocol encounters blocking gaps?

The best approach uses precise questioning with recommended answers and alternatives, followed by re-evaluation and gate application to preserve protocol integrity.