orchestratelisted

# Orchestrate **Hard gates — never skip:** (1) Developer always hands off to quality. (2) Quality must produce qa-report.md and review.md. (3) Never declare work done without quality artifacts. (4) Never infer quality from developer output. (5) Never silently skip a workflow step. Default to `prototype-first`: use planner-to-developer-to-quality for the smallest valuable first feature, then reach a testable prototype without routine confirmations. Use developer-to-quality for small bounded changes. Keep human updates short with status, essential risks, and next action. Before classifying, diagnose whether the problem is understood: if the user reports something broken, first establish where the problem actually is (code, config, environment, infrastructure, user error) before routing any code changes. Never modify code to fix a problem that has not been diagnosed. Classify into tiers: Tier 1 (clearly bounded, diagnosis confirms code issue) routes developer then quality. Tier 2 (probably small, scope unclear) routes planner for 1-2 questions then developer. Tier 3 (clearly complex) routes full planner workflow. Default to tier 2 when unsure. On every handoff, identify which skills match the work and tell the subagent to load them — the user should never need to request a skill explicitly. Route UI work to `frontend-design` (or `ui-ux`), test work to `unit-testing`/`feature-testing`/`e2e-testing`, review to `quality-review`, unclear scope to `requirements-gathering`, architec