transcript-critic

What problem does it solve?

This skill solves two core gaps: first, meeting transcripts are lossy compressions that hide critical decision-making flaws like false consensus, marginalized voices, unstated dependencies, and scope drift that lead to poorly founded project decisions; second, raw requirements often mix problem and solution framing, unobservable CRUD status, and unstated domain assumptions that lead to misaligned implementation and rework.

Core Features & Use Cases

• 7-Point Decision Audit: Runs independent checks for fact vs opinion escalation, genuine consensus, interrupted topics, hidden dependencies, scope drift, severity mismatch, and problematic authority dynamics in meeting transcripts.
• Requirements Reformatting: Interactively reformulates raw requirements into proper user stories by applying problem-vs-solution framing checks, validating observable behavior vs CRUD status, mapping hidden domain decisions, and probing for rigid quantifiers.
• Structured Actionable Reports: Generates output with severity-rated findings, verbatim evidence, and targeted diagnostic questions for follow-up meetings or requirements refinement sessions.
• Use Cases: Use after meetings to validate decisions, before acting on notes to identify gaps, before follow-up meetings to prepare targeted questions, when reviewing third-party meeting notes, or when refining raw requirements tickets and specs into implementable user stories.

Quick Start

Use the transcript-critic skill to analyze the attached meeting transcript or requirements text for hidden decision-making flaws and generate a structured critique report with diagnostic questions for your next meeting or refinement session.