sanity-check

Identify and tag assumptions in plans with verification statuses.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/AGM1968/weave --skill sanity-check-agm1968
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sanity-check
Source: https://github.com/AGM1968/weave/tree/main/.claude/skills/sanity-check
Command: npx skills add https://github.com/AGM1968/weave --skill sanity-check-agm1968

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and validate assumptions before implementation to prevent design errors or failure cascades.

Core Features & Use Cases

  • Assumption discovery and tagging
  • Verification guidance and confidence tracking
  • Risk-aware decision gating for planning and design reviews

Quick Start

Ask the AI to surface hidden assumptions and document them for verification.

Frequently Asked Questions about sanity-check

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

FAQPage Schema
How do I identify hidden assumptions in a project plan before implementation?

Assumption validation involves identifying and documenting all assumptions within a plan, then explicitly tagging them as verified, unverified, uncertain, or falsified during design reviews to prevent failure cascades.

What is the best way to validate project assumptions during design reviews?

Validating assumptions during design reviews involves applying risk-aware decision gating to track verification confidence and provide explicit guidance for confirming uncertain requirements or environments.

How do I document unverified requirements and track their verification status?

Document unverified requirements by applying explicit tags like verified, unverified, uncertain, or falsified, and track verification confidence throughout the guided workflow to manage design risks.

Can I use assumption tagging for risk management in uncertain environments?

Yes, assumption tagging supports risk management by documenting uncertain environmental factors and applying a guided verification workflow to gate planning decisions based on tracked confidence levels.

When do I need to surface assumptions to prevent failure cascades in software planning?

Surface assumptions during planning and design phases when requirements or environments are uncertain, preventing failure cascades by validating decisions and tracking confidence before implementation begins.

Does sanity-check work without external dependencies for planning validation?

Sanity-check operates without external dependencies, allowing you to independently document assumptions and execute the verification workflow directly within your current planning and design environment.