Phase 3 — design the Angular feature, decompose into TDD-shaped frontend tasks, write ADRs. Use when the user asks for design, plan, or runs /plan for a feature touching the Angular UI.
Phase 7 — pre-commit review of changed Angular files; produce findings in 08-code-review.md covering correctness, accessibility, performance, security, test quality, and clarity. Use when running /review for features that touch Angular source.
Phase 4 (green/refactor/simplify) — minimum Angular production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
Phase 1+2 — author and review the EARS-lite spec for a Spring Boot 4 feature. Use proactively when the user asks for a spec, requirements, or runs /spec or /spec-review.
Phase 3 — design the Spring Boot 4 feature, decompose into TDD-shaped tasks, write ADRs. Use proactively when the user asks for design, plan, or runs /plan.
Phase 7 — pre-commit human-style review against the full diff and validation report. Produce 08-code-review.md and final verdict; block commit on unwaived blockers.
Phase 4 (green/refactor/simplify) — minimum production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.
Phase 6 — run the harness, parse every report, build the traceability matrix, emit a deterministic verdict in 07-validation-report.md and 07a-traceability.md.