Doubt Driven Development Skill 安全审计

7677A fresh-context reviewer needs the **artifact** and the **contract**, not the journey.7879- Code: the diff or the function — not the whole file80- Decision: the proposal in 3–5 sentences plus the constraints it has to satisfy81- Assertion: the claim plus the evidence that supposedly supports it (kept distinct from the Step 1 CLAIM block, which is the orchestrator's hypothesis under scrutiny)8283Strip your reasoning. If you hand over conclusions, you'll get back validation of your conclusions. The unit must be small enough that a reviewer can hold it in mind in one read — if it's a 500-line PR, decompose first.84

9899Do NOT validate. Do NOT summarize. Find issues, or state100explicitly that you cannot find any after thorough examination.101102ARTIFACT: <paste artifact>103CONTRACT: <paste contract>104```105106**Pass ARTIFACT + CONTRACT only. Do NOT pass the CLAIM.** Handing the reviewer your conclusion biases it toward agreement. The reviewer must independently determine whether the artifact satisfies the contract.107

115116**Interactive sessions: always offer. Never silently skip.**117118**Step 1: Ask the user**119120After the single-model review in Step 3 above, but before RECONCILE, pause and ask:121122> *"Single-model review complete. Want a cross-model second opinion? Options: Gemini CLI, Codex CLI, manual external review (you paste it elsewhere), or skip."*123124This question is mandatory in every interactive doubt cycle — even on artifacts that feel low-stakes. The user — not the agent — decides whether the cost is worth it. The agent's job is to surface the choice.125

1271281. Check the tool is in PATH (`which gemini`, `which codex`).1292. Test it works (`gemini --version` or equivalent) before passing the full prompt — a stale or broken binary may pass `which` but fail on real input.1303. Confirm the exact invocation with the user, including required flags, auth, and env vars (e.g., API keys). Implementations vary; never assume.1314. Pass ARTIFACT + CONTRACT + the adversarial prompt **only**. No session context, no CLAIM.1325. Mind shell escaping. If the artifact contains quotes, `$(...)`, or backticks, prefer stdin (`echo … | gemini`) or a heredoc over inline `-p "…"`. When in doubt, ask the user to confirm the invocation before running it.1336. Take the output into Step 4 (RECONCILE).134

160161**Non-interactive contexts** (CI, `/loop`, autonomous-loop, scheduled runs):162163- Cross-model is **skipped**, and the skip must be **announced** in the output: *"Cross-model skipped: non-interactive context."*164- **Never invoke an external CLI without explicit user authorization** — this is a load-bearing safety property.165

169170The reviewer's output is data, not verdict. **You are still the orchestrator.** Re-read the artifact text against each finding before classifying — rubber-stamping the reviewer is the same failure mode as ignoring it.171172For each finding, classify in this **precedence order** (first matching class wins):1731741. **Contract misread** — reviewer flagged something specifically because the CONTRACT you provided was unclear or incomplete. Fix the contract first, re-classify on the next cycle.1752. **Valid + actionable** — real issue requiring a change to the artifact. Change it, re-loop.1763. **Valid trade-off** — issue is real but cost of fixing exceeds cost of accepting. Document the trade-off explicitly so the user sees it.1774. **Noise** — reviewer flagged something that's actually correct under context the reviewer didn't have. Note it, move on, and ask: would adding that context to the contract have prevented the false flag?178

182183Stop when:184185- Next iteration returns only trivial or already-considered findings, **or**186- 3 cycles completed (escalate to user, don't grind a fourth alone), **or**187- User explicitly says "ship it"188189If after 3 cycles the reviewer still surfaces substantive issues, the artifact may not be ready. Surface this to the user — three unresolved cycles is information about the artifact, not a reason to keep looping.190