verify-architecture

Architecture trace validation aligns plan decisions with GOAL.md success criteria and SPEC.md acceptance criteria. It checks traceability across plan, spec, and goal, flagging orphan decisions to prevent drift before task breakdown begins.

Architecture traceability ensures every architecture decision serves defined goals and acceptance criteria. You need it when orchestrating workflows with SPEC.md, GOAL.md, and plan.md to prevent scope creep and misalignment.

Orphan decision detection identifies architecture choices in plan.md that lack traceability to GOAL.md or SPEC.md. It provides route guidance back to plan for trace completion, ensuring all decisions serve defined goals.

Yes, this architecture audit applies to orchestration workflows containing SPEC.md, GOAL.md, and plan.md. These files provide the success criteria and acceptance criteria needed to validate architecture decision coverage and alignment.

When checks fail, the process provides clear failure routing hints and withholds outputs arch-report.md and status.json. It routes you back to complete missing traceability between architecture decisions and success criteria.

Architecture drift happens when decisions lack traceability to goals and acceptance criteria. Early feedback guardrails prevent over-engineering by validating coverage of all success criteria in architecture decisions before task breakdown.