What problem does it solve? Project documentation often drifts from reality: stale status gets copied forward, proposals read like implemented features, and polished prose hides weak evidence. This Skill produces durable documentation that accurately represents verified system state without inventing facts or flattening evidence classes. ## Core Features & Use Cases - Evidence-preserving drafting: Distinguishes artifact-backed, runtime-verified, human-observed, inferred, proposed, and unknown states so claims stay proportional to actual proof. - Typed document workflows: Provides structured guidance for handoffs, SOPs/runbooks, ADRs, release notes, READMEs, and acceptance/build reports. - Staleness and claim control: Binds documents to version, commit, artifact, and environment scope, and blocks inflated claims like treating compiled code as runtime-verified. - Use Case: After a release candidate passes verification, use this Skill to write release notes that state the exact build identity, verified behavior, limitations, rollback state, and explicit non-claims instead of generic marketing copy. ## Quick Start Use the signalproof-document skill to write a handoff document for the current project state based only on verified evidence, with open gates and non-claims listed explicitly.
