rewrite-specs

Rewriting design documentation to reflect an approved architecture involves hard-rewriting specs, behavior matrices, and named invariants into present-tense end-state language. This removes obsolete claims entirely, ensuring the implementation team has a single authoritative source of truth.

Updating obsolete specifications after a design brainstorm requires an explicit approved direction input to hard-rewrite existing docs. This process codifies the new architecture into authoritative substrate, removing contradictions and future-tense claims before implementation begins.

Yes, you can isolate design spec rewrites in a git worktree to ensure changes are reviewed as a coherent diff. This operates exclusively on a dedicated design branch, allowing changes to be discarded without affecting the main codebase if needed.

To commit rewritten specs for downstream validation, you produce an atomic commit on a dedicated design branch with a mandatory Classification trailer. This trailer categorizes the rewrite as Pure implementation, Design, or Mixed for the review process.

Rewriting design docs removes obsolete claims entirely instead of annotating them as deprecated. This hard-rewrite approach ensures all behavior matrices and named invariants use present-tense end-state language, preventing confusion during implementation.

You need to codify an approved feature direction into authoritative substrate during post-brainstorm workflows. When a refactor or architecture direction is approved, rewriting specs into end-state docs prevents confusion and makes tracking changes easier.