doubt-driven-development

仓库创建 2026年7月5日最近提交 21 天前SkillHot 收录 21 天前

▸ 精选理由

适合高风险或关键逻辑的额外把关流程。

这个 Skill 做什么

通过新环境的对抗性复核在关键决定前寻找缺陷。

在关键决定前用“怀疑者”角度做一次对抗性复核，刻意寻找设计或实现里的假设漏洞，而不是去确认它没问题。适合在正确性比速度重要、涉及生产或安全敏感逻辑、或者在不熟悉的代码区时使用。特点是模拟一个新上下文的审查者，目标是推翻而非批准，成本远低于事后修复。

▸ 展开 SKILL.md 英文原文

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

Skill 开发管理审查制对抗性评审质量保障通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/kulapoo/opencode-agent-harness/main/skills/doubt-driven-development/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/kulapoo/opencode-agent-harness/main/skills/doubt-driven-development/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Doubt-Driven Development

## Overview

A confident answer is not a correct one. Long sessions accumulate context that quietly turns assumptions into "facts" without anyone noticing. Doubt-driven development is the discipline of materializing a fresh-context reviewer — biased to **disprove**, not approve — before any non-trivial output stands.

This is not `/review`. `/review` is a verdict on a finished artifact. This is an in-flight posture: non-trivial decisions get cross-examined while course-correction is still cheap.

## When to Use

A decision is **non-trivial** when at least one of these is true:

- It introduces or modifies branching logic
- It crosses a module or service boundary
-

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有