design-doc-required

To enforce a design document requirement before writing code, use a hard gating mechanism that blocks source file edits until a validated design doc and coding-summary are confirmed. This prevents premature implementation and avoids undocumented assumptions.

You need a coding-summary file before the first line of implementation when proposing new requirements, behavior-changing refactors, or bug fixes. It extracts full-path class lists and method-level guidance to ensure implementation matches the validated design document.

To validate Mermaid diagrams in a software design doc, enforce specific diagram types and subgraph/box grouping rules, then delegate syntax validation to markdown-writing-standards. This ensures architecture decisions remain auditable and consistent.

Blocking source code edits before architecture discussion improves compliance by preventing premature analysis. It ensures formal design documents are validated, project indexes are updated via doc-index-required Phase-A and Phase-B, and documentation boundaries are verified.

The best way to structure pre-implementation design documents is placing them in a docs/design/ directory using -current.md and -coding.md files, while reading docs/00_project_overview.md to load project knowledge and route required readings before any edits.

You cannot run source file edits without a matching design doc and coding file. The hard gate blocks any Edit or Write operations until both the design document and the corresponding coding-summary are confirmed present and compliant.