architect

Create a software architecture plan by applying universal phase patterns and checklists to structure atomic, reversible phases. This enforces dependency discipline, validation criteria, rollback considerations, and formal phase headers with conventional commit guidance.

Preventing architectural drift requires using universal design patterns and checklists during the plan phase. This ensures the implementation plan remains well-structured, auditable, and enforces strict dependency discipline and risk ordering at every step.

Risk management in phase planning works by ordering implementation steps to isolate failures early. It enforces dependency discipline by validating prerequisites at each step, ensuring atomic phases remain testable and reversible before proceeding.

Yes, you can use universal design patterns to review and refactor existing feature architectures. Applying structured checklists during the plan phase validates current implementations and generates auditable plans with explicit phase headers and rollback considerations.

You need formal phase headers and conventional commit guidance when an implementation plan requires strict auditability and atomic execution. This structure enforces validation criteria and rollback considerations for every individual phase.

Universal checklists focus on structural plan generation, risk ordering, and dependency validation rather than generating code or executing the implementation. They provide architectural guidelines but do not automate the actual software development or deployment process.