cross-framework-audit-synthesis

Synthesizes accessibility, usability, and heuristic audit findings into one prioritized remediation backlog.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/vmitsaras/Agent-Skills --skill cross-framework-audit-synthesis-vmitsaras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-framework-audit-synthesis
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/research-synthesis/cross-framework-audit-synthesis
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill cross-framework-audit-synthesis-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple specialist reviews (WCAG accessibility, Universal Design, Nielsen heuristics, Norman principles) cover the same interface, teams end up with duplicated findings, conflicting severities, and inflated issue counts. This Skill consolidates those outputs into one evidence-based audit report with deduplicated root-cause findings and a dependency-aware remediation plan. ## Core Features & Use Cases - Contract-validated intake: Validates every incoming finding against the shared finding contract from inclusive-interface-audit-orchestrator, classifying each as valid, normalizable, invalid, or conflicting. - Root-cause deduplication: Merges findings only when symptom, target, root cause, and remediation locus all match, preserving every source ID, occurrence, and valid framework mapping. - Evidence-based prioritization: Scores findings on user impact, likelihood, task criticality, reach, and remediation dependency to assign P0–P4 priorities and phased remediation plans. - Use Case: After running separate WCAG, Nielsen, and usability audits on a checkout flow, feed all specialist reports to this Skill to receive one canonical finding ledger, a conflict log, critical-flow risk table, and a verification plan. ## Quick Start Synthesize the attached WCAG, Nielsen heuristic, and usability audit reports into one consolidated audit report with a prioritized remediation backlog.

Frequently Asked Questions about cross-framework-audit-synthesis

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

FAQPage Schema
How do I combine multiple accessibility audit reports into one backlog?▼

Provide each specialist report along with the shared finding contract, and the synthesis validates every finding, merges duplicates sharing a root cause, and outputs one canonical finding ledger with P0–P4 priorities and phased remediation steps.

How are duplicate WCAG and heuristic findings deduplicated?▼

Findings merge only when they share the same user-observable symptom, target behavior, supported root cause, and remediation locus. All source IDs, occurrences, and valid framework mappings are preserved even after merging.

Does this skill perform the accessibility audits itself?▼

No. It only synthesizes completed specialist review outputs. To plan which audits to run, use the inclusive-interface-audit-orchestrator skill, and use individual specialist skills for WCAG, Nielsen, or Universal Design reviews.

Can heuristic observations be reported as WCAG failures?▼

No. WCAG criterion results stay separate from heuristic and inclusive-design observations. A heuristic concern becomes a WCAG failure only with criterion-specific conformance evidence, and unsupported mappings go to the conflict ledger.

What happens when specialist audits disagree on severity or root cause?▼

Disagreements are recorded in a conflict ledger with evidence on each side. Conflicts resolve only through documented decision rules, never by majority vote, and unresolved cases get a targeted manual test assignment.

What are the limitations of cross-framework audit synthesis?▼

It cannot certify WCAG conformance, invent missing evidence, or treat absent findings as passes. Without the orchestrator's shared finding contract, it returns only a clearly labeled provisional synthesis rather than a contract-valid result.