Menu
QA 验收流水线编排器：从需求变更分析到功能测试、回归测试、集成测试， 维护持久化测试用例库，输出 qa-report.md。 Use when: 测试人员对新功能或 release 进行验收测试，需要完整的功能测试覆盖。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Read-only cross-artifact consistency analysis after planning and before approval. Verifies that spec.md, requirements.json, plan.md, tasks/Tn.md, traceability.json are mutually consistent: no duplicate/ambiguous requirements, every behavior mapped to a task, no orphan tasks, no coverage gaps, no contradictions. Outputs artifact-analysis.json with coverage% and severity. CRITICAL/HIGH findings block the approval gate. Use when: planning produced plan.md + tasks + traceability.json, before the user approves the plan.
Explore 2-3 implementation options with trade-offs when the user describes a new feature or requirement. Use when: the user asks for a new feature design, implementation options, or technical trade-off analysis.
After implementation and before final verification, compare current code/tests against the intent inventory (requirements.json + traceability.json). Classify each requirement/behavior as covered, missing, partial, contradicts, or unrequested. Append missing/partial/contradicts as new tasks back to executing. Repeat until converged: zero blocker findings. Outputs convergence-report.json. Use when: executing produced test-report.md but before loom-verification-before-completion.
Expand each requirement into verifiable Behavior Obligations across 15 fixed dimensions (happy-path, boundary, invalid-input, authorization, state-transition, idempotency, concurrency, atomicity, external-failure, compatibility, security, performance, observability, recovery, forbidden-behavior) before planning. Use when: brainstorming produced requirements.json and spec is approved, but behaviors are still placeholders or only happy-path; before loom-writing-plans.
Read-only adversarial reviewer that looks for what SHOULD exist but doesn't, by cross-checking Behavior Obligations against code, tests, expected side effects, forbidden side effects, failure scenarios, and public API changes. Focuses on negative space: events that should not repeat, permissions that should not be bypassed, partial writes that should not happen, old APIs that should not change, swallowed exceptions, leaked secrets. Outputs findings.json. Use when: executing or converge needs an independent omission sweep.
Analyze user request + collect signals (file scope, keywords, worktree state, spec existence), then select pipeline steps via rule short-circuit / AI fallback / rule-based fallback. Select steps first, expose the choice to the user, and persist selected dynamic_steps only after explicit user confirmation; pipeline-plan.md is optional for manual review. Use when: user is unsure which pipeline type to pick, or wants AI to choose steps automatically.
| name | loom-qa |
| description | QA 验收流水线编排器：从需求变更分析到功能测试、回归测试、集成测试， 维护持久化测试用例库，输出 qa-report.md。 Use when: 测试人员对新功能或 release 进行验收测试，需要完整的功能测试覆盖。 |
| when_to_use | Run QA acceptance for a feature or release, including functional, regression, and integration coverage. |
| argument-hint | <feature, release, or target spec> |
| user-invocable | true |
这是测试人员使用的流水线，与开发流水线完全独立。运行于功能开发完成后，目标是：
.loom/qa-suite/），功能变更时同步更新用例QA 流水线（pipeline_type: qa）有 6 个阶段，每个阶段对应本 skill 的不同职责：
| 阶段 | 职责 | 使用子 prompt |
|---|---|---|
qa-analysis | 分析变更范围，确定测试矩阵 | qa-analyst-prompt.md |
qa-design | 生成/更新用例，旧用例转 deprecated | qa-designer-prompt.md |
qa-approved | human-approval gate（自动） | — |
qa-execution | 跑自动化测试，生成手动 checklist | qa-executor-prompt.md |
qa-signoff | human-approval gate，测试人员签字 | — |
qa-report | 汇总 → qa-report.md | qa-reporter-prompt.md |
qa/<date+target>/（不复用 specs/）.loom/qa-suite/，进版本控制，随功能迭代更新PASS（全绿）/ PARTIAL（自动绿但手动有遗留）/ FAIL（有测试失败）loom run --spec-dir qa/<target> --verdict，exit 0=PASS，1=FAIL，2=PARTIALqa/<date+target>/handoffs/<stage>.json，摘要说明阶段结论、关键产物、未决风险和下一阶段注意事项；不要把完整测试日志写进 handoff。# 初始化 qa 战役
loom run --type qa --spec-dir qa/$(date +%Y-%m-%d)+<target>
# 推进各阶段
loom run --spec-dir qa/<target> --advance --compression-confirmed
# 人工审批节点
loom run --spec-dir qa/<target> --approve
# CI 门禁查询
loom run --spec-dir qa/<target> --verdict
references/qa-analyst-prompt.mdreferences/qa-designer-prompt.mdreferences/qa-executor-prompt.mdreferences/qa-reporter-prompt.mdQA 阶段产物和对应 handoffs/<stage>.json 均完成后，先压缩旧阶段原始测试过程和长日志，再带压缩确认推进状态机；qa-report 作为终止阶段也必须写入 qa-report.md 与 handoffs/qa-report.json。