Docs As Definition Of Done

Use when finishing any code change that modifies behavior, public API, CLI flags, config shape, defaults, error messages, or anything a reader-of-the-docs would model — before committing, pushing, or declaring "done." Forbids deferring doc updates to a follow-up commit, ticket, or "cleanup later."

veegee82 Updated 2 repo stars
Four axes of gradient descent — code (θ), deliverable (y), method (m), reasoning chain (t) — with LDD as the optimizer

File contents

veegee82/loss-driven-development commit 8c95d77e09

Frequently asked questions

npx get-skill add veegee82/docs-as-definition-of-done