08-3-report

name: "08-3-report-健檢總結" description: "Use when: 健檢第三階段、證據式健康報告、健檢深度摘要、功能/端點/命令覆蓋率、紅黃綠燈號、未驗證/阻塞清單、證據等級摘要、優先修復清單與行動建議。DO NOT use when: 尚未完成前兩階段健檢。" metadata: author: antigravity version: "2.0" origin: framework kind: workflow platforms: ["codex"] lifecycle_phase: audit role: analyst memory_awareness: read tool_scope: ["filesystem:read", "filesystem:write:logs", "terminal:read"] human_gate: "none" automation_safe: false

總監可讀輸出契約（Director-Readable Output Contract）

Director-facing output MUST use a context-sensitive plain-language structure before technical details:

• Routine discussion, short status updates, and simple judgments may use concise paragraphs or short lists.
• Implementation plans, pre-write risk reviews, multi-file changes, completion summaries, audit reports, and handoffs MUST use a table or structured summary.
• When a table is used, prefer this compact table:
• The 位置 column MUST name the concrete location in plain language, then add the file path, section heading, tool/status scope, or directory scope in parentheses. If the item is not a single file, say so explicitly, e.g. 工作區狀態（git status）, 管理器巡檢工具（框架來源倉庫限定：Scripts/AI-RulesManager.ps1）, or 規則與技能範圍（部署後：.codex、.agents/skills；框架來源倉庫限定：Codex/.codex、Shared/skills）.
• Formal short lists or paragraph-led summaries may use compact scope labels, but abstract labels such as 核心規範, 工作流入口, 文件說明, 巡檢規則, or 記憶卡 MUST be resolved in the same response through a 位置索引 section.
• The 位置索引 section MUST map each compact label to a concrete file, section heading, tool/status scope, or directory scope. Do not leave compact labels as unexplained categories.

Technical details may only appear after a 補充技術細節 section when they are necessary. File names and other code identifiers may appear only inside parentheses after a plain-language label, e.g. 建構流程規則（03-build-建構/SKILL.md）. Do not describe changes only with function names, variable names, metadata fields, schema fields, command parameters, or internal tool names.

技術詞彙翻譯閘門（Technical Vocabulary Translation Gate）:

• Director-facing text MUST NOT contain bare code identifiers. A bare identifier is a function name, variable name, schema field, metadata key, command parameter, internal tool name, or file path shown outside parentheses after a plain-language label.
• Every mention of any technical identifier MUST use this order: plain-language label first, then the technical identifier only inside parentheses, e.g. 建構流程規則（03-build-建構/SKILL.md）.
• Technical identifiers MUST NOT appear as standalone subjects, standalone list items, or unexplained table values. If the exact identifier is not needed for location, omit it.
• When repeated later, keep the same plain-language label and parenthetical identifier when needed. Do not switch back to the bare code name.

中立誠實協作與知識新鮮度契約（Neutral Honest Collaboration and Freshness Gate）:

• Maintain a neutral, honest stance: do not optimize for pleasing, flattering, appeasing, or automatically agreeing with the Director. Treat the Director's goal as the target, then verify claims against actual files, tool output, official documentation, or reliable primary sources.
• Support proposals when evidence and feasibility align. If evidence conflicts with the proposal, respond with: 我看到的事實 / 可能問題 / 建議做法.
• Do not object merely to appear critical. When rejecting, narrowing, or changing a proposal, provide a workable alternative aligned with the Director's goal.
• Treat memory and internal model knowledge as possibly stale. Current local files and tool output override memory; official documentation or primary sources override internal model knowledge.
• For high-change information — external frameworks, APIs, package versions, platform rules, pricing, laws, security guidance, recent status, or anything uncertain — retrieve current or official information before architecture, code, recommendations, or decisions.
• Anchor verification with the project version first. If no version is available, use the current date/year as the time anchor. If current verification is unavailable, say it is not verified and do not present memory as current fact.

source-command-08-audit-08-3-report-skill

Use this skill when the user asks to run the migrated source command 08_audit(健檢)-08-3_report-SKILL.

Command Template

[SKILL: /08_audit — Phase 3: 證據式健檢總結報告]

本工作流彙整 Phase 1 + Phase 2 objects, including audit depth, inventories, coverage, and evidence packets. It uses audit-engine/references/report-gates.md for all final status decisions.

3.1 Evidence Normalization Gate

Before writing the final report:

• Every red, yellow, unverified, or blocked item must have an evidence packet.
• Every not_applicable item must cite project surface profile evidence.
• Every deep or forensic critical inventory item must have covered, partial, unverified, blocked, or not-applicable status.
• Every evidence packet for a known inventory item must include the inventory id.
• High-risk green items must include a short evidence summary.
• Missing real evidence cannot be converted to green by confidence language.
• Scanner output, screenshots, or AI semantic suspicion must not be reported as confirmed defects without matching evidence.
• Sampling limits must be stated when the audit depth is quick or standard, or when a deep audit could not cover the full denominator.

3.2 Traffic-Light Dashboard

Output only applicable categories and explain omitted ones:

3.3 Evidence Summary

Include:

• Selected audit depth and reason.
• Inventory coverage counts by features, endpoints, commands, jobs, interfaces, data flows, performance targets, and risks.
• Evidence level counts.
• Unverified checks.
• Blocked checks with smallest missing condition.
• Not-applicable checks with surface-profile reason.
• Sampling limits and unreviewed areas.
• Intermediate report paths if .agents/logs/audit/<timestamp>/ was used.

3.4 Coverage Summary

Report coverage with denominators instead of vague confidence:

3.5 Priority Action Items

Sort by severity, business impact, and evidence strength:

Do not recommend source edits directly from an audit report. Route follow-up work through the correct governed workflow.

3.6 Location Index

If compact labels are used, map each label to a concrete file, section, tool/status scope, command output, report path, or directory scope.

3.7 Completion

Append:

「[健檢完成] 本次報告採證據優先判定，並依健檢深度列出盤點覆蓋率。缺少真實證據的項目已標記為未驗證或阻塞，不列為綠燈；抽樣結果不會被宣稱為全量通過。如需修復指定項目，請依優先級交給修復、測試、架構、例行巡檢或發布治理工作流。」

[SECURITY & COMPLIANCE MANDATE]

Inherits: .agents/skills/_shared/_security_footer.md (Role Lock Gate)

• Role: Reader | 純報告彙整；只允許寫入健檢摘要日誌，不修改原始碼或記憶卡。

MCP 記憶證據沿用 08 入口與 .agents/skills/memory-ops/references/memory-mcp-tool-contract.md；子流程只能使用唯讀 cartridge-system 證據，缺少 MCP 工具時標記未驗證或阻塞，不得直接改記憶。