pre-adr-introspect

What problem does it solve?

It prevents wasted work and production-risky rework by forcing early introspection of existing architectural canon before proposing any new ADR, schema change, or architectural pattern.

Core Features & Use Cases

• Pre-write canon detection: searches existing ADRs, references, migrations, and controllers to identify already-established patterns and avoid duplication.
• Schema/endpoint precedent validation: checks recent migrations and API/controller conventions to confirm whether a similar pattern already exists.
• Collision/conflict guardrails: verifies ADR numbering conventions and documented conflict-resolution rules to avoid same-day numbering collisions.
• Production-state diagnosis when required: runs targeted DB checks when the ADR includes an executable runbook plan that depends on current data.
• Contract/pattern alignment: verifies whether there are canonical reference documents for the topic to avoid reinventing already-contractual design choices.
• Practical ADR output: produces a short checklist-style report summarizing themes, candidate ADR number status, related canon links, production diagnostics, and the reuse/extend/create decision.

Quick Start

Activate pre-adr-introspect before creating or proposing any new memory/decisions/NNNN-*.md ADR, schema addition, or architectural pattern, then follow the five checklist items and include the generated report in the ADR context.