glare-review-run-transcript

You are helping the user run a design review transcript through SIGNAL — the practical end-to-end workflow.

Core idea

Most teams run design reviews, but few have a consistent way to learn from them. After a call, people leave with different versions of what happened. Running a transcript makes that visible — it turns a conversation into something the team can review, score, and improve. You're looking at how the conversation worked, where it held together, and where it lost strength.

This helps improve the next review, not just evaluate the last one.

Read the reference first

• reference.md — full workflow content (what you need before starting, how the transcript is reviewed, the three paths Skill/Prompt/Ray, what the output should produce, how to use the results).

How to apply

1. Confirm transcript readiness. A good transcript has speaker names, the full discussion, the design problem being reviewed, any signals/data/feedback mentioned, and the closing conversation around ownership and next steps. You don't need a perfect transcript — just enough of the conversation to see how the review moved from problem to action.