Skills › Compound Engineering › ce-riffrec-feedback-analysis › compound-engineering-feedback-format.md
compound-engineering-feedback-format.md
116 lines · skills/ce-riffrec-feedback-analysis/references/compound-engineering-feedback-format.md at 3449230
Most marks come from matching words in the file, so treat them as pointers.
1# Compound Engineering Feedback Format
3Use this shape when converting Riffrec evidence into a durable brainstorm or planning input.
Compound Engineering Feedback Format
Use this shape when converting Riffrec evidence into a durable brainstorm or planning input.
Raw lines 1 to 45## Finding
7```markdown
8### F1. <Short problem title>
10- **Severity:** P0/P1/P2/P3
11- **Observed:** <What happened, grounded in transcript/events/screenshots>
12- **Expected:** <What the user appeared to expect or what the product should do>
13- **Evidence:** <Moment IDs and screenshot links>
14- **Confidence:** High/Medium/Low, with reason
15- **Requirement candidates:** R1, R2
16```
Finding
### F1. <Short problem title>
- **Severity:** P0/P1/P2/P3
- **Observed:** <What happened, grounded in transcript/events/screenshots>
- **Expected:** <What the user appeared to expect or what the product should do>
- **Evidence:** <Moment IDs and screenshot links>
- **Confidence:** High/Medium/Low, with reason
- **Requirement candidates:** R1, R218## Requirements Kickoff
20```markdown
21---
22date: YYYY-MM-DD
23topic: <topic>
24---
26# <Topic Title>
28## Problem Frame
30<Who is affected, what is changing, and why it matters.>
32---
34## Actors
36- A1. User: <Role in the recorded workflow>
37- A2. Product surface: <System under test>
38- A3. Agent/assistant, if relevant: <Role in the workflow>
40---
42## Key Flows
44- F1. Recorded feedback triage
45 - **Trigger:** A Riffrec capture bundle is available for review.
46 - **Actors:** A1, A2
47 - **Steps:** <3-7 product steps seen in the recording>
48 - **Outcome:** <What should be true after the fix>
49 - **Covered by:** R1, R2
51---
53## Requirements
55**Observed product behavior**
56- R1. <Concrete product behavior requirement>
58**Feedback evidence and reviewability**
59- R2. <Requirement about making the issue observable or preventing recurrence>
61---
63## Acceptance Examples
65- AE1. **Covers R1.** Given <state>, when <action>, <outcome>.
67---
69## Success Criteria
71- <Human outcome>
72- <Downstream agent handoff quality>
74---
76## Scope Boundaries
78- <Deliberate non-goal>
80---
82## Key Decisions
84- <Decision>: <Rationale>
86---
88## Dependencies / Assumptions
90- <Material dependency or assumption>
92---
94## Outstanding Questions
96### Resolve Before Planning
98- <Only product questions that block planning>
100### Deferred to Planning
102- [Technical] <Questions better answered during codebase exploration>
104---
106## Next Steps
108-> Invoke `ce-brainstorm` to confirm, correct, and regroup the captured requirements before any planning.
109```
Requirements Kickoff
---
date: YYYY-MM-DD
topic: <topic>
---
# <Topic Title>
## Problem Frame
<Who is affected, what is changing, and why it matters.>
---
## Actors
- A1. User: <Role in the recorded workflow>
- A2. Product surface: <System under test>
- A3. Agent/assistant, if relevant: <Role in the workflow>
---
## Key Flows
- F1. Recorded feedback triage
- **Trigger:** A Riffrec capture bundle is available for review.
- **Actors:** A1, A2
- **Steps:** <3-7 product steps seen in the recording>
- **Outcome:** <What should be true after the fix>
- **Covered by:** R1, R2
---
## Requirements
**Observed product behavior**
- R1. <Concrete product behavior requirement>
**Feedback evidence and reviewability**
- R2. <Requirement about making the issue observable or preventing recurrence>
---
## Acceptance Examples
- AE1. **Covers R1.** Given <state>, when <action>, <outcome>.
---
## Success Criteria
- <Human outcome>
- <Downstream agent handoff quality>
---
## Scope Boundaries
- <Deliberate non-goal>
---
## Key Decisions
- <Decision>: <Rationale>
---
## Dependencies / Assumptions
- <Material dependency or assumption>
---
## Outstanding Questions
### Resolve Before Planning
- <Only product questions that block planning>
### Deferred to Planning
- [Technical] <Questions better answered during codebase exploration>
---
## Next Steps
-> Invoke `ce-brainstorm` to confirm, correct, and regroup the captured requirements before any planning.111## Evidence Rules
113- Prefer moment IDs and screenshot links over prose-only claims.
114- Mark visual interpretation as an inference when the screenshot does not prove intent.
115- Requirements should describe product behavior, not implementation details.
116- Do not include absolute local paths in CE docs; use repo-relative paths when possible.
Evidence Rules
- Prefer moment IDs and screenshot links over prose-only claims.
- Mark visual interpretation as an inference when the screenshot does not prove intent.
- Requirements should describe product behavior, not implementation details.
- Do not include absolute local paths in CE docs; use repo-relative paths when possible.