Update to Compound Engineering

{
  "description": "Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.",
  "included_files": [
    {
      "relative_path": "references/analyzer.md",
      "size_in_bytes": 1387
    },
    {
      "relative_path": "references/compound-engineering-feedback-format.md",
      "size_in_bytes": 2368
    },
    {
      "relative_path": "references/extensive-analysis.md",
      "size_in_bytes": 8197
    },
    {
      "relative_path": "references/install-riffrec.md",
      "size_in_bytes": 1941
    },
    {
      "relative_path": "references/quick-bug-report.md",
      "size_in_bytes": 2971
    },
    {
      "relative_path": "scripts/analyze_riffrec_zip.py",
      "size_in_bytes": 53829
    }
  ],
  "name": "ce-riffrec-feedback-analysis",
  "skill_md_contents": "---\nname: ce-riffrec-feedback-analysis\ndescription: \"Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.\"\n---\n\n# Riffrec Feedback Analysis\n\nTurn raw product feedback into structured evidence for downstream agents. This skill is the consumption side of [Riffrec](https://github.com/kieranklaassen/riffrec), a capture tool that records synchronized screen + voice + event sessions and emits a `riffrec-*.zip` bundle.\n\n**Done:**\n\n- Setup ends with a current capture/share path.\n- Quick analysis ends with one evidence-backed bug report and no durable artifact unless requested.\n- Extensive analysis ends with the complete evidence set and a `ce-brainstorm` handoff unless the user asked for extraction only.\n- A missing input, analyzer failure, or unresolved route ends with an actionable blocker rather than a partial success claim.\n\n## Choose the path\n\nRoute from the input. Read only the references named for that route; do not load the other path references.\n\n- **Setup** — user has no recording yet and asks how to install Riffrec, capture a session, or share feedback. Read `references/install-riffrec.md`.\n- **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/analyzer.md`, then `references/quick-bug-report.md`.\n- **Extensive analysis** — input is longer, contains multiple issues, requirements, or a workflow walkthrough, or the user wants requirements material. Read `references/analyzer.md`, then `references/extensive-analysis.md`. Continue into `ce-brainstorm` unless the user explicitly asked only to extract or analyze artifacts.\n\nWhen 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.\n\n## Common rules\n\n- Keep raw recordings, audio chunks, zip contents, session dumps, and extracted screenshots local-only by default. Do not commit `raw/` or `frames/` directories unless the user explicitly asks and privacy is acceptable.\n- Text/metadata artifacts (requirements kickoff material, analysis summaries, problem analyses, source manifests) may be committed when they are needed for traceability and contain no sensitive data.\n- Use repo-relative screenshot paths in any committed doc so later agents can open the evidence without absolute local paths.\n\nThe Compound Engineering output format used by the extensive path is documented in `references/compound-engineering-feedback-format.md`.\n"
}