doubt-driven-development
仓库创建 2026年2月16日最近提交 22 小时前SkillHot 收录 20 天前
▸ 精选理由
适合高风险或安全敏感场景,提升决策健壮性。
这个 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.
8.1w
Stars
8.7k
Forks
24
仓库内 Skill
+10.0k
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/addyosmani/agent-skills/main/skills/doubt-driven-development/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/addyosmani/agent-skills/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 公开信息 · 原文版权归作者所有