assumption-extractor

Extract and classify assumptions from technical documents by risk impact.

1|Updated Jan 10, 2026

Search Tags:#verification #assumptions #risk assessment #technical documents #design plans #implicit assumptions

Ready to run

npx skills add https://github.com/tomwangowa/agent-skills --skill assumption-extractor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: assumption-extractor
Source: https://github.com/tomwangowa/agent-skills/tree/main/assumption-extractor
Command: npx skills add https://github.com/tomwangowa/agent-skills --skill assumption-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill surfaces hidden assumptions in technical documents before they become expensive surprises, treating technical plans as collections of testable claims.

Core Features & Use Cases

Assumption Identification: Systematically extracts explicit and implicit assumptions from technical documents.
Classification: Classifies each assumption by visibility, verification status, recommended verification method, and risk impact.
Use Case: Before implementing a new microservice, use this Skill to audit the design document for any unstated assumptions about API compatibility or performance, ensuring critical risks are addressed upfront.

Quick Start

Use the assumption-extractor skill to extract assumptions from the document at /docs/design.md, focusing on the decision of migrating to Playwright.

Frequently Asked Questions about assumption-extractor

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

FAQPage Schema

How do I extract implicit assumptions from a technical design document?▼

Assumption auditing reviews technical plans to surface hidden claims before implementation. You extract implicit assumptions, classify them by visibility and verification status, and assess risk impact to ensure critical design risks are addressed upfront.

When do I need to audit assumptions in a feasibility assessment?▼

You audit assumptions in a feasibility assessment before committing to implementation. This process surfaces hidden risks about API compatibility or performance, ensuring critical technical risks are addressed upfront before they become expensive surprises.

How do I classify extracted assumptions by risk impact and verification status?▼

You classify extracted assumptions by visibility, verification status, recommended verification method, and risk impact. This systematic classification treats each technical plan as a collection of testable claims to address critical risks upfront.

Can I use this to surface hidden assumptions about API compatibility in a microservice design plan?▼

Yes, you can use this to audit microservice design plans for unstated assumptions about API compatibility or performance. It systematically extracts and classifies hidden assumptions, ensuring critical risks are addressed before implementation.

What is the best way to verify explicit claims in technical documents before implementation?▼

The best way to verify explicit claims in technical documents is to systematically extract them, classify by visibility, and assign a recommended verification method. This audits the plan for unstated risks before committing to implementation.