proof

把 Markdown 文档送到 Proof editor 做 human-in-the-loop 协作评审。

基本信息

字段	内容
Skill	proof
类型	internal-only
研发链路位置	Spec
入口	internal_only
Source	skills/proof/SKILL.md

描述

Create, share, view, comment on, edit, and run human-in-the-loop review loops over markdown documents via Proof, the collaborative markdown editor at proofeditor.ai ("Proof editor"). Use when the user wants to render or view a local markdown file in Proof, share markdown to get a URL, iterate collaboratively on a Proof doc, comment on or suggest edits in Proof, HITL a spec/plan/draft for human review, sync a Proof doc back to local, or work from a proofeditor.ai URL. Trigger on phrases like "view this in proof", "share to proof", "iterate with proof", or "HITL this doc", and on spec-brainstorm / spec-ideate / spec-plan handoffs for human review. Also match clear requests for a rendered/shared markdown review surface even if the user does not name Proof. Do not trigger on "proof" meaning evidence, math/logic proof, burden of proof, proof-of-concept, or bare "proofread this" requests where inline text review is expected.

何时使用

• 需求、计划或草稿需要人类协作 review。
• 需要生成 Proof 链接或同步 Proof 文档。
• workflow 交接点需要 HITL 确认。

工作步骤

• 读取用户意图、代码库背景、已有 requirements、历史学习和外部证据。
• 收敛问题框架、用户流、边界、验收标准或候选方向。
• 区分必须现在解决的问题和可延后到计划或实现阶段的问题。
• 把 WHAT 层证据交给 plan 或 doc-review。

输出

• requirements、ideation artifact、scope boundaries 或 open questions。
• 可供计划阶段追溯的 actors、flows、acceptance examples 和关键决策。

Agent 调度

• 可按需要引入 spec-flow、product、design、security、repo、web 或 issue research agents。
• agent 产出是证据和问题发现，最终需求边界仍由当前 workflow 汇总。

边界

• 不适合数学证明或一般 proofread 语义。
• Proof 评审不替代 deterministic validation。