documentation-placement

What problem does it solve?

Disorganized documentation leads to wasted time searching, outdated information, and a lack of clarity on project status and architectural decisions, hindering team collaboration and project progress.

Core Features & Use Cases

• Timeline-Based Placement: Defines where documentation belongs (e.g., coordination/ for planning, dev/docs/ for implementation) based on its creation timeline, ensuring logical organization.
• Documentation-First PR Protocol: Enforces merging documentation (like ADRs) before code implementation, ensuring design clarity and alignment before development begins.
• Active Work Status Board: Provides a template and protocol for ACTIVE-WORK.md to mitigate worktree isolation and enhance visibility of ongoing tasks and their status.
• Use Case: Before starting a new feature, create an Architecture Decision Record (ADR) in docs/adr/ and merge it first, then reference it in the implementation PR, ensuring a documentation-first approach that saves rework.

Quick Start

Determine the correct placement for a new design blueprint created during the D3 phase.