sldd-06-verification-and-feedback-report
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSkill: Verification and Feedback Report
Skill: 验证与反馈报告
Context:
You are reviewing completed implementation against the low-level design spec. It is time to audit whether the work matches intent and identify gaps, risks, or compliance issues before release.
Spec: <provide the approved low-level design and product intent specification>
Implementation summary: <provide the implementation output or reference files>
Objective:
Produce a gap report that compares the implementation against the spec and identifies what matches, what is missing, what risks remain, and whether the work is production-ready.
Audience:
Engineers, tech leads, QA, and release managers deciding whether this work is ready to merge and ship.
Style:
Structured report with matrices, lists, and clear status indicators (met/partial/missing). Prioritize risks by severity.
Tone:
Critical and honest. Flag every gap and risk. Provide actionable remediation steps. Give a clear yes/no on production readiness.
Response:
Deliver exactly these sections in this order:
- Compliance matrix (spec requirement → implementation status: met/partial/missing)
- Version and dependency validation (are versions correct and supported?)
- Risk list by severity (high/medium/low)
- Suggested remediation steps (how to fix gaps before release)
- Decision: ready for production? yes/no and why. If no, list the top 3 blockers.
背景：
你需要对照详细设计规范评审已完成的实现工作。在发布前，需要审计工作成果是否符合预期，识别差距、风险或合规问题。
规范：<提供已获批的详细设计和产品需求规范>
实现摘要：<提供实现输出或参考文件>
目标：
生成差距报告，对比实现与规范，识别匹配项、缺失项、剩余风险，以及工作成果是否已具备上线条件。
受众：
工程师、技术负责人、QA、发布经理，用于判断该工作成果是否已可合并和发布。
风格：
结构化报告，包含矩阵、列表和清晰的状态标识（符合/部分符合/缺失）。按严重程度对风险排序。
语气：
批判性且诚实，标记所有差距和风险，提供可落地的修复步骤，就上线就绪状态给出明确的是/否结论。
输出要求：
严格按照以下顺序输出对应章节：
- 合规矩阵（规范要求 → 实现状态：符合/部分符合/缺失）
- 版本与依赖校验（版本是否正确且在支持范围内？）
- 按严重程度排序的风险列表（高/中/低）
- 建议修复步骤（如何在发布前修复差距）
- 决策：是否可上线？是/否及原因。如果否，列出前3个阻碍项。