sot-reconcile

Consolidate six L4 audit verdicts into a reconciled argument graph.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/speplinski/hackathon-opus-47 --skill sot-reconcile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sot-reconcile
Source: https://github.com/speplinski/hackathon-opus-47/tree/main/skills/sot-reconcile
Command: npx skills add https://github.com/speplinski/hackathon-opus-47 --skill sot-reconcile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates six L4 audit verdicts into a single, graph-based reconciliation artifact that surfaces cross-skill insights such as violations, corroborations, contradictions, tensions, and gaps for auditable design decisions.

Core Features & Use Cases

  • Graph-primary reconciliation of six cross-skill verdicts into a unified structure.
  • Derives consumer-facing flat lists (ranked_violations, tensions, gaps) from the graph for downstream decision-making.
  • Use to surface cross-skill tensions, align verdicts, and present auditable recommendations.

Quick Start

Provide a cluster context and six L4 verdicts to produce a graph-based reconciliation artifact.

Frequently Asked Questions about sot-reconcile

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

FAQPage Schema
How do I reconcile multiple design audit verdicts into a single structure?

Design audit verdict reconciliation consolidates six L4 audit verdicts into a single graph-based structure. This process surfaces cross-skill alignments, tensions, and prioritized actions for auditable design decisions across Norman, Accessibility, Kahneman, Osterwalder, Cooper, and Garrett frameworks.

What is a reconciliation graph for cross-skill design audits?

A cross-skill reconciliation graph is a unified structure that maps audit verdicts using node types for violation, corroboration, contradiction, tension, and gap. It preserves source verdicts for traceability while surfacing prioritized actions derived from overlapping design framework evaluations.

How do I create an argument graph from L4 audit data?

To create an argument graph from L4 audit data, provide a cluster context and six L4 verdicts as input. The system generates a graph-based reconciliation artifact that derives consumer-facing flat lists, including ranked violations, tensions, and gaps for downstream decision-making.

Can I use design audit reconciliation for accessibility and cognitive evaluations?

Yes, design audit reconciliation applies across Norman, Accessibility, Kahneman, Osterwalder, Cooper, and Garrett verdicts. It surfaces cross-skill tensions and contradictions between accessibility requirements, cognitive load evaluations, and business model frameworks into one auditable graph.

What's the best way to surface tensions and gaps across multiple design frameworks?

The best way to surface tensions and gaps across design frameworks is through graph-primary reconciliation. This approach maps contradictions and gaps as distinct node types, preserving source verdicts for traceability while deriving prioritized actions and ranked violations.

Do I need all six L4 verdicts to generate a reconciliation graph?

Generating a reconciliation graph requires six L4 audit verdicts representing Norman, Accessibility, Kahneman, Osterwalder, Cooper, and Garrett evaluations. The process consolidates these specific verdicts to surface cross-skill alignments, tensions, and prioritized actions accurately.