Riffrec Feedback Analysis

Turn raw product feedback into structured evidence for downstream agents. This skill is the consumption side of Riffrec, a capture tool that records synchronized screen + voice + event sessions and emits a riffrec-*.zip bundle.

Choose the path

Route to the matching reference based on the input. Read only that reference; do not load the others.

• Setup — user has no recording yet and asks how to install Riffrec, capture a session, or share feedback. Read references/install-riffrec.md.
• Quick bug report — input is a short recording (under ~60 seconds), the user describes a single specific issue, or asks for "quick", "small", or "just transcribe". Read references/quick-bug-report.md. Emit one concise bug report; skip the full artifact set and brainstorm handoff.
• Extensive analysis — input is a longer recording, contains multiple issues / requirements / workflow walkthroughs, or the user wants requirements or brainstorm material. Read references/extensive-analysis.md. Always continue into the brainstorm skill.

When the input is ambiguous (e.g., a zip arrived without context), inspect the recording length and event count before choosing. If still unclear, ask the user which path applies before running anything heavy — present the three paths (Setup / Quick bug report / Extensive analysis) through the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_user in Gemini/Pi. Fall back to a numbered list in chat only when no blocking tool exists or the call errors. Never silently skip the question.

Issue storage (GH preflight)

Both the quick and extensive paths store their durable output as a GitHub issue, never a local file. Run the GH preflight before any issue read/write — abort with the guidance shown if any check fails; NEVER fall back to a local file (the analyzer's temp scaffolds are working material, not the durable artifact). The Setup path does not touch issues, so it skips this.

1. gh installed. If not: tell the user to install it from https://cli.github.com or run /tunan:setup.