decision-accountability

Analyze architectural decisions for epistemic and ownership failures.

104|31|Updated Dec 10, 2025

Search Tags:#complexity analysis #decision analysis #architecture review #cost comparison #tech debt prevention

Ready to run

npx skills add https://github.com/jacob-dietle/context-os --skill decision-accountability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-accountability
Source: https://github.com/jacob-dietle/context-os/tree/main/.claude/skills/decision-accountability
Command: npx skills add https://github.com/jacob-dietle/context-os --skill decision-accountability

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps ensure that architectural decisions, code, and specs are based on verified assumptions and accountability, preventing costly rewrites and maintaining system integrity.

Core Features & Use Cases

Decision Accountability: Verifies assumptions and catches corner-cutting, applying to code, specs, data models, auth flows, and context structures.
Complexity Analysis: Checks complexity claims by implementing the feature to verify its complexity.
Cost Comparison: Evaluates the cost of deferring work now versus later.

Quick Start

Use the decision-accountability skill to review the architecture decision for the new authentication system.

Frequently Asked Questions about decision-accountability

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

FAQPage Schema

How do I verify architectural assumptions to prevent tech debt?▼

To verify architectural assumptions, analyze decisions for epistemic failures and ownership gaps alongside complexity claims. This validates code, specs, data models, and auth flows to ensure system integrity and prevent tech debt.

What is complexity analysis in architecture review?▼

Complexity analysis in architecture review checks complexity claims by implementing the feature to verify its actual difficulty. This validates whether proposed architectural complexity is justified or represents corner-cutting that creates future tech debt.

How do I evaluate the cost of deferring architecture work?▼

Evaluating the cost of deferring architecture work requires comparing the cost of deferring work now versus implementing it later. This deferral cost analysis prevents technical debt accumulation by quantifying the downstream impact of postponed architectural decisions.

Can I use decision accountability analysis for auth flows and data models?▼

Decision accountability analysis applies directly to auth flows, data models, code, specs, and context structures. It verifies assumptions and catches corner-cutting across these architectural components to maintain system integrity and prevent future rewrites.

When should I conduct an architecture review for decision integrity?▼

Conduct an architecture review for decision integrity when evaluating new systems like authentication flows to verify assumptions and prevent costly rewrites. This catches epistemic failures and ownership gaps before they create technical debt in production.