check-assumptions

Verify decisions by challenging assumptions against known behavioral patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bogheorghiu/ex-cog --skill check-assumptions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-assumptions
Source: https://github.com/bogheorghiu/ex-cog/tree/main/vasana-system/skills/check-assumptions
Command: npx skills add https://github.com/bogheorghiu/ex-cog --skill check-assumptions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams avoid acting on unverified assumptions by forcing explicit verification against behavioral patterns before proceeding. It prompts critical thinking, surface contradictions, and strengthens decision accountability.

Core Features & Use Cases

  • Verification protocol: checks decisions against known patterns (e.g., optimization bias, bulk operation risks) and requires explicit evidence.
  • Pattern references: references the pattern library and related vasana notes to ground decisions in documented knowledge.
  • Decision documentation: produces a traceable decision record with assumptions and verifications for future audits.

Quick Start

Ask me to challenge a decision by verifying assumptions against known behavioral patterns before proceeding.

Frequently Asked Questions about check-assumptions

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

FAQPage Schema
How do I verify assumptions before making a critical architecture decision?

Checking assumptions against behavioral patterns prevents bulk operation risks by forcing explicit verification steps against documented patterns, ensuring convenience does not override capability before acting.

How do I document decision records for risk management and future audits?

Checking assumptions against behavioral patterns prevents bulk operation risks by forcing explicit verification steps against documented patterns, ensuring convenience does not override capability before acting.

What is the best way to challenge a tool recommendation against behavioral patterns?

Checking assumptions against behavioral patterns prevents bulk operation risks by forcing explicit verification steps against documented patterns, ensuring convenience does not override capability before acting.

Why does convenience override capability in bulk operations and how to prevent it?

Checking assumptions against behavioral patterns prevents bulk operation risks by forcing explicit verification steps against documented patterns, ensuring convenience does not override capability before acting.

Can I use pattern verification for architecture choices and bulk operations?

Checking assumptions against behavioral patterns prevents bulk operation risks by forcing explicit verification steps against documented patterns, ensuring convenience does not override capability before acting.