siege-analytics

Definition Of Done Rules — Development skill for Claude Code

Development community

Always-on Definition of Done.

How to install Definition Of Done Rules

Installs to ~/.claude/skills/siege-analytics-claude-configs-public-_definition-of-done-rules/SKILL.md

Terminal

mkdir -p ~/.claude/skills/siege-analytics-claude-configs-public-_definition-of-done-rules && curl -fsSL https://raw.githubusercontent.com/siege-analytics/claude-configs-public/HEAD/skills/_definition-of-done-rules.md -o ~/.claude/skills/siege-analytics-claude-configs-public-_definition-of-done-rules/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Definition Of Done Rules does

description: Always-on Definition of Done. Applied to every behavior change. Five hard criteria plus two opt-in -- review, edge cases, tests, ticket update, ticket existence, KB delta, multi-layer decomposition. No soft carve-outs on (a)-(e).

Definition of Done

Code is not finished until **all five** of the following are true. This is a gate, not a recommendation. PRs that fail any criterion don't merge; sessions that fail any criterion don't end.

The five criteria

a. Code-r

Alternatives in Development

Clawgod — This is NOT a third-party Claude Code client 837 ★
New Project — Create a new project with all scaffolding rules applied 335 ★
HERO Anti OverDefense — HERO = Hashing · Edge cases · Rubrics · Overbuild — the four shapes coding agents over-defend in 333 ★