describe-docs-system

What problem does it solve?

Without a centralized docs location and explicit governance, project documentation tends to drift out of date, causing confusion and misalignment with code.

Core Features & Use Cases

• Centralized docs location: .ushabti/docs/ as the single source of truth.
• Role-based responsibilities to ensure documentation is planned, implemented, and reviewed in lockstep with code.
• Use Case: During a Phase, the Scribe consults docs before planning; during implementation, the Builder updates docs; during review, the Overseer verifies alignment.

Quick Start

Review and update docs under .ushabti/docs/ to ensure alignment with current code changes.