everyinc/compound-engineering-plugin

ce-riffrec-feedback-analysis

Analyze recorded product feedback into evidence for bugs and requirements.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-riffrec-feedback-analysis

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.

Done:

  • Setup ends with a current capture/share path.
  • Quick analysis ends with one evidence-backed bug report and no durable artifact unless requested.
  • Extensive analysis ends with the complete evidence set and a ce-brainstorm handoff unless the user asked for extraction only.
  • A missing input, analyzer failure, or unresolved route ends with an actionable blocker rather than a partial success claim.

Choose the path

Route from the input. Read only the references named for that route; do not load the other path references.

  • 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/analyzer.md, then references/quick-bug-report.md.
  • 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.

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.

Common rules

  • 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.
  • 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.
  • Use repo-relative screenshot paths in any committed doc so later agents can open the evidence without absolute local paths.

The Compound Engineering output format used by the extensive path is documented in references/compound-engineering-feedback-format.md.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
everyinc
コミュニティ

ce-compound

Capture a solved problem's lesson in its cheapest durable form, a test or lint rule, a coding standard, or a repo learning, or refresh existing learnings against the codebase. Use when verified work corrected a wrong belief about how something behaves, such as a failed approach, a real defect a review caught, or a wrong assumption or document, or when auditing stale, overlapping, or drifted learnings. Do not auto-invoke it for work that went as first planned.

1時間の導入数
1
GitHub Stars
2.6万
更新日
11月18日
everyinc
コミュニティ

ce-plan

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

1時間の導入数
1
GitHub Stars
2.6万
更新日
11月18日
everyinc
コミュニティ

ce-setup

Check Compound Engineering's tools and repo config and fix what it finds, scaffold a Compound Pack with pack: , or draft and refresh coding standards and review docs from pull request history. Use when setting up or diagnosing Compound Engineering, or when creating or updating CODINGSTANDARDS.md or REVIEW.md, including on a schedule.

1時間の導入数
1
GitHub Stars
2.6万
更新日
11月18日
everyinc
コミュニティ

ce-simplify-code

Simplify code for clarity, reuse, quality, and efficiency while preserving behavior, and prune tests and comments that carry no value. Use after implementation and before review, or to audit tests or comments in any part of a repo; use ce-debug for bugs.

1時間の導入数
1
GitHub Stars
2.6万
更新日
11月18日