task-breakdown

Fallback for user-facing interface work when frontend-design is unavailable; keep UI clear, accessible, responsive, and intentional without unnecessary…

Use when reviewing a ticket diff for correctness, regressions, architecture, security, and maintainability.

Use when classifying engineering work, selecting a fast or full workflow path, and coordinating agent handoffs.

Use before implementation when checking repository state, selecting a branch, or protecting uncommitted work.

Use when validating a completed feature against its acceptance criteria through integrated behavior.

Use when a user journey or cross-service behavior needs end-to-end validation.

Use when an approved, human-requested deployment specifically targets Vercel.

Use when creating or running focused automated tests for isolated logic and edge cases.

Use when deploying to a VPS via GitHub Actions and Docker.

Use when a request needs product discovery, scope, acceptance criteria, constraints, or high-value clarification questions.

Use only for a human-requested deployment after QA PASS and review APPROVE have been recorded.

Use when translating approved requirements into a solution design, architecture fit, risks, and test strategy.