|
1 | 1 | --- |
2 | 2 | name: delivery-video |
3 | | -description: Produce trustworthy delivery/acceptance demo videos of real, working software — recorded from actual screen sessions with narration, subtitles and a deterministic quality gate. Use when the user says "record a delivery video", "make a feature demo", "acceptance demo video", "录交付视频", "录个演示", "功能演示", "验收演示视频", "给客户看的功能 demo". Renders real recordings only — no static screenshots, mocks or old footage stitched into a "demo". |
| 3 | +description: Produce trustworthy delivery/acceptance demo videos — or defect/feedback report videos — from real screen recordings with narration, subtitles and a deterministic quality gate. Use when the user says "record a delivery video", "make a feature demo", "acceptance demo video", "bug report video", "record the defect", "录交付视频", "录个演示", "功能演示", "验收演示视频", "问题反馈视频", "缺陷复现视频", "把 bug 录下来". Renders real recordings only — no static screenshots, mocks or old footage stitched into a video. |
4 | 4 | metadata: |
5 | 5 | short-description: Record, render and gate trustworthy delivery demo videos |
6 | 6 | --- |
@@ -37,6 +37,8 @@ A delivery is done only when all of these hold: |
37 | 37 |
|
38 | 38 | A passing gate is not the user's acceptance. Posting to a ticket or group is a delivery action — do it only when the user asks in that turn; public upload or publishing waits for an explicit "send". |
39 | 39 |
|
| 40 | +For an `intent: "feedback"` episode the same evidence rules apply, but the result state is the **defect still being reproduced**: the last segment must show the wrong behaviour or its explicit impact, never a fix that was not actually proven. |
| 41 | + |
40 | 42 | ## Workflow |
41 | 43 |
|
42 | 44 | ### 1. Define what this demo must prove |
@@ -167,11 +169,48 @@ In the target project (not inside this skill) write `delivery.md`: environment & |
167 | 169 |
|
168 | 170 | Reply with the conclusion first, then the artifact path, duration, gate result, SHA256 and the unproven items. Never just "the video is done". |
169 | 171 |
|
| 172 | +## Feedback mode (defect evidence) |
| 173 | + |
| 174 | +The same renderer and gate also produce bug/feedback videos. Set `intent: "feedback"` and add an `issue` block; delivery episodes stay unchanged when the fields are absent. |
| 175 | + |
| 176 | +```json |
| 177 | +{ |
| 178 | + "intent": "feedback", |
| 179 | + "voice": "zh-CN-YunxiNeural", |
| 180 | + "issue": { |
| 181 | + "id": "BUG-123", |
| 182 | + "title": "保存金额后列表仍显示旧总额", |
| 183 | + "severity": "major", |
| 184 | + "environment": "staging / build <version>", |
| 185 | + "expected": "保存后列表立即显示新的总额", |
| 186 | + "actual": "返回列表仍显示旧总额,必须整页刷新才更新", |
| 187 | + "repro": ["打开订单详情", "把金额改为 1200", "保存并返回列表"] |
| 188 | + }, |
| 189 | + "segments": [ |
| 190 | + {"id": "01-repro", "phase": "repro", "label": "复现", "shot": "take-01.mp4", |
| 191 | + "start": 0.5, "end": 12.0, "text": "照着三个步骤操作,保存后回到列表。"}, |
| 192 | + {"id": "02-actual", "phase": "actual", "label": "现象", "shot": "take-01.mp4", |
| 193 | + "start": 12.0, "end": 20.0, "text": "列表这里仍然是旧总额,和刚才保存的数值对不上。"} |
| 194 | + ] |
| 195 | +} |
| 196 | +``` |
| 197 | + |
| 198 | +Rules: |
| 199 | + |
| 200 | +- `issue.title`, `issue.severity`, `issue.expected`, `issue.actual` are required. `severity` is one of `blocker`, `critical`, `major`, `minor`. `id`, `environment` and `repro` are optional. |
| 201 | +- At least one segment must carry `phase: "actual"`. Allowed phases: `context`, `repro`, `actual`, `expected`, `impact`. |
| 202 | +- The severity becomes the first on-screen chip and the phase the second, so a viewer can tell repro from symptom without narration. |
| 203 | +- During `phase: "repro"` segments the renderer overlays the first five `issue.repro` steps in the top-right. Keep steps short; the full list stays in the generated report. |
| 204 | +- A feedback video reports what the current build does. Do not mix in footage from an older build, do not claim a fix, and do not hide a passing case to make the defect look worse. |
| 205 | +- `render.py` writes `feedback.json` (issue, segment phases, artifact SHA256) and `feedback.generated.md` — a ticket-ready draft with expected/actual, numbered repro steps, per-segment source ranges and the gate result. `verify_delivery.py` fails a feedback episode whose JSON report is missing or bound to another file. |
| 206 | +- `feedback.generated.md` is overwritten on every render. Treat it as the source for the ticket; add impact and business context in a separate note or edit a copy, do not hand-edit the generated file. |
| 207 | + |
170 | 208 | ## Common shapes |
171 | 209 |
|
172 | 210 | - Web/desktop UI: window-level recording cropped to the content area; controls, feedback and read-back all in frame. |
173 | 211 | - CLI/API: dedicated terminal recording real commands and real responses; mask tokens, internal hosts and debug logs. |
174 | 212 | - Multi-case acceptance (recommended for 2+ cases): one real run per case, one result segment per case; the `case` field becomes the chip, and narration covers only that case's delta and result. |
| 213 | +- Defect report: one continuous take that reproduces the problem, with `phase` segments for repro and actual; the `expected` state can be one narration line or a separate real segment when an earlier build is legitimately available. |
175 | 214 | - No visual UI: show real API responses, logs or data — never fabricate a fake UI to stand in for the product. |
176 | 215 | - Engineering acceptance: terminal and evidence frames are fine, but lead with the business conclusion. |
177 | 216 |
|
|
0 commit comments