creative-qa

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Creative QA

Follow shared release-shell rules in:

```
postplus-shared
```
release-shell rules

Use this skill after a human has actually reviewed an asset.

This skill is for:

recording human judgments about generated assets
preserving why something was approved, revised, or rejected
pointing feedback back to the stage that should change
turning review notes into structured data for later analysis

This skill is not for autonomous AI approval.

请遵循

postplus-shared

发布框架中的共享规则：

```
postplus-shared
```
发布框架规则

请在人工实际审核完资产后使用该Skill。

该Skill适用于：

记录人工对生成资产的判定结果
留存资产通过、修订或被驳回的原因
将反馈指向需要调整的环节
将审核记录转化为结构化数据，以便后续分析

该Skill不适用于AI自主审批。

Core Idea

核心理念

The first version should assume:

humans decide quality
AI may help summarize or prefill observations
only human-confirmed feedback becomes the durable QA record

If there is no human feedback yet, there may be no QA record yet. That is acceptable.

第一版应遵循以下假设：

由人工判定质量
AI可协助总结或预填观察结果
只有经人工确认的反馈才会成为持久保存的QA记录

如果尚未有人工反馈，则暂时不会生成QA记录，这是可接受的情况。

Human Rule

人工规则

Do not invent a final verdict on behalf of a human reviewer.

Allowed:

turn human notes into structured fields
normalize categories
suggest likely blame stages

Not allowed:

silently approving an asset
replacing a human verdict with an AI guess

不得代人工审核者做出最终判定。

允许操作：

将人工记录转换为结构化字段
统一类别规范
建议可能需要负责的环节

禁止操作：

擅自通过资产
用AI猜测替代人工判定

Objects

对象

1. QA Report

1. QA报告

One review record tied to one asset version.

Should include:

```
qaReportId
```
```
targetObjectType
```
```
targetObjectId
```
```
targetVersion
```
```
reviewer
```
```
verdict
```
```
goodReasons
```
```
badReasons
```
```
issueCategories
```
```
blameStage
```
```
proposedAction
```

一份审核记录对应一个资产版本。

应包含以下字段：

```
qaReportId
```
```
targetObjectType
```
```
targetObjectId
```
```
targetVersion
```
```
reviewer
```
```
verdict
```
```
goodReasons
```
```
badReasons
```
```
issueCategories
```
```
blameStage
```
```
proposedAction
```

2. Feedback Record

2. 反馈记录

An optional follow-up object that can be consumed by rerun workflows.

Should include:

```
feedbackId
```
```
qaReportId
```
```
feedbackCategory
```
```
feedbackText
```
```
dependencyImpact
```
```
rerunTarget
```

一个可选的后续对象，可被重运行工作流调用。

应包含以下字段：

```
feedbackId
```
```
qaReportId
```
```
feedbackCategory
```
```
feedbackText
```
```
dependencyImpact
```
```
rerunTarget
```

Scope

适用范围

This skill should support human review records for:

```
image
```
```
voice_take
```
```
video_render
```
```
final_export
```

该Skill应支持对以下类型资产的人工审核记录：

```
image
```
```
voice_take
```
```
video_render
```
```
final_export
```

Local Persistence Convention

本地存储规范

Store QA next to the asset being reviewed.

In the released product shell:

keep draft QA notes or intermediate review payloads under
```
<work-folder>/.postplus/creative-qa/
```
keep the final confirmed QA record next to the reviewed asset or final deliverable

One possible project-local layout is:

text

<work-folder>/.postplus/creative-qa/video-render/
  qa-v1.json

or:

text

reviews/voice-take-1.review.json

The key requirement is stable linkage back to the reviewed object.

将QA记录存储在被审核资产的同级目录下。

在发布产品框架中：

将草稿QA记录或中间审核数据存储在
```
<work-folder>/.postplus/creative-qa/
```
目录下
将最终确认的QA记录存储在被审核资产或最终交付物的同级目录下

一种可行的项目本地目录结构示例：

text

<work-folder>/.postplus/creative-qa/video-render/
  qa-v1.json

或：

text

reviews/voice-take-1.review.json

核心要求是确保记录与被审核对象的关联稳定。

Review Categories

审核类别

Common issue categories:

```
lip_sync
```
```
persona_drift
```
```
audio_style
```
```
audio_pacing
```
```
hook_weak
```
```
ad_like
```
```
ugc_native_feel
```
```
visual_realism
```
```
subtitle_accuracy
```
```
mixed
```

Common blame stages:

```
image
```
```
script
```
```
voice
```
```
render
```
```
subtitle
```
```
mixed
```

常见问题类别：

```
lip_sync
```
```
persona_drift
```
```
audio_style
```
```
audio_pacing
```
```
hook_weak
```
```
ad_like
```
```
ugc_native_feel
```
```
visual_realism
```
```
subtitle_accuracy
```
```
mixed
```

常见责任环节：

```
image
```
```
script
```
```
voice
```
```
render
```
```
subtitle
```
```
mixed
```

Output Rule

输出规则

The QA layer should answer:

what was reviewed
who reviewed it
what they decided
why they decided it
what should happen next

Read

references/qa-schema.md

when creating or updating these files.

QA层应明确回答以下问题：

审核的对象是什么
谁进行的审核
审核结果是什么
得出该结果的原因
下一步应采取什么行动

创建或更新这些文件时，请参考

references/qa-schema.md

。