speckit-architecture-guard-architecture-apply

To update plan.md and tasks.md with approved architecture refactor findings, apply an architecture-guard write-back workflow that rewrites these planning artifacts. This ensures review outputs and refactor tasks are reflected as explicit follow-up work while preserving feature intent and scope.

Architecture write-back for spec-kit plan management is the process of directly updating planning artifacts to reflect approved architecture changes. It reorders and refines tasks so architectural dependencies and boundaries become explicit within the existing workflow.

To apply Constitution rules to existing planning artifacts, execute a write-back procedure that optionally reflects approved Constitution Update Proposals as follow-up work. This constrains changes to allowed artifacts and keeps edits incremental and non-blocking.

Yes, the architecture refactor write-back process preserves original feature scope. It ensures incremental edits that are small and targeted, keeping changes non-blocking to maintain product intent and workflow continuity throughout the planning artifact updates.

A limitation of automated architecture write-back is that it constrains changes strictly to allowed artifacts like plan.md and tasks.md. You should not use it for sweeping scope changes; it targets only approved refactor tasks and boundaries to preserve workflow continuity.