loom-doubt-driven-developmentlisted

# loom-doubt-driven-development Doubt-driven development is an in-flight challenge playbook. It names the claim, extracts the smallest reviewable artifact and contract, runs a Ralph-backed challenge when the claim risk warrants it, reconciles findings, and routes durable output through audit, evidence, tickets, specs, research, or constitution. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-ralph`, `loom-audit`, `loom-evidence`, `loom-tickets`, `loom-specs`, `loom-research`, `loom-constitution`, `loom-retrospective`, and `loom-knowledge`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. Use this playbook for review posture. Use `loom-audit` when the challenge result should be recorded as an audit. ## Use This Playbook When Use this playbook when a claim is non-trivial, including: - branching logic or invariants changed - a module, service, storage, API, or worker boundary changed - safety depends on ordering, idempotency, concurrency, caching, auth, permissions, migration, compatibility, or external behavior - an implementation asserts it matches a spec or acceptance criterion - a high-risk diff appears correct but would be expensive to debug later - the current context has become invested in one interpretation Skip it for mechanical renames, formatting, obvious one-line changes, simple file moves, and local summaries. ## Route Use this ro