Skip to content
Back to skills

Assumption Excavation

ASecurity

Surface hidden assumptions in plans, specs, AGENTS.md, SKILL.md, SET bundles, and workflow contracts before implementation or handoff. Use when an artifact looks plausible but may rely on unstated environment, dependency, behavioral, temporal, or success assumptions.

  • 16 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added September 5, 2026
ai-agentsrails

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add markoblogo/abvx-agent-skills --skill assumption-excavation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Assumption Excavation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Assumption Excavation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/markoblogo-assumption-excavation/badge)](https://www.skillsdirectory.com/skills/markoblogo-assumption-excavation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: assumption-excavation
description: Surface hidden assumptions in plans, specs, AGENTS.md, SKILL.md, SET bundles, and workflow contracts before implementation or handoff. Use when an artifact looks plausible but may rely on unstated environment, dependency, behavioral, temporal, or success assumptions.
license: MIT
metadata:
  abvx_status: experimental
  abvx_origin: adapted
---

# Assumption Excavation

Find what the artifact takes for granted before those assumptions become implementation bugs.

## Use When

- reviewing PRDs, specs, plans, or issue slices before work starts;
- reviewing `AGENTS.md`, `SKILL.md`, SET bundles, proof-loop contracts, or workflow docs;
- a proposal sounds confident but depends on unclear prerequisites;
- you need a lightweight pre-implementation review lens.

## Workflow

1. Identify the artifact and its intended consumer.
2. Read for implicit assumptions, not prose quality.
3. Classify assumptions:
   - environment: tools, services, files, auth, OS, network;
   - dependency: upstream state, input shape, prior checks;
   - behavioral: what humans, agents, or systems are expected to do;
   - temporal: what must remain stable over time;
   - success: what the artifact counts as done or safe.
4. Rank the assumptions by fragility:
   - high: likely to break or expensive if wrong;
   - medium: plausible risk with manageable fallout;
   - low: visible but not blocking.
5. Mark partially surfaced assumptions as `PARTIAL`.
6. Recommend what must be clarified, tested, or accepted before implementation.

## Output Shape

Use:

- verdict: `EXAMINED` or `UNEXAMINED`;
- top assumptions, ranked;
- fragility score or severity per item;
- missing evidence;
- smallest clarification or verification step.

## Guardrails

- Do not rewrite the artifact unless asked.
- Do not treat assumptions as errors by default; some are deliberate.
- Do not block on low-risk assumptions.
- State uncertainty as text-based inference, not mind reading.

## Provenance

Adapted from the `assumption-excavator` pattern in `aself101/agents-and-pipelines`, compressed for ABVX skill use and broader repo-contract review.

Files in this skill

  • SKILL.md2.1 KB
  • SKILL_CARD.md1.4 KB
  • agents/openai.yaml249 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…