django-absurd

Use when a change touches user-facing behavior — management commands or their flags, TASKS / OPTIONS settings, the enqueue or params API, defaults, the setup flow, or system checks, or project conventions. Keeps README.md, the AGENTS.md integration guide, the docs/web/ documentation site, the runnable example (examples/), CLAUDE.md (maintenance), and design decisions in docs/WHY.md (via capture-why) in sync with the code so updates don't get lost in context.

Use when cutting a django-absurd release to PyPI — deciding the next version (with the

Use when cleaning up docs/specs and docs/plans — retiring specs/plans that are obsolete or already captured in docs/WHY.md. Records each in docs/HISTORY.md with a recoverable git SHA link before deleting it. Run after capture-why.

Use when refreshing docs/WHY.md or consolidating the project's durable reasoning from docs/specs and docs/plans — e.g. specs/plans have accumulated, or before retiring them. Captures intent and load-bearing "why", never current structure.