planning-quality-gates

Quality gates for planning enforce mandatory checks on external SDKs, API calls, third-party integrations, and CDN resources. Document retry strategies, error handling, timeouts, and offline detection for each external dependency before delivery to catch integration gaps early.

Planning quality gates require specifying retry logic, timeout strategy, error handling, offline detection, and loading states for WebSocket and network operations. Define these mechanisms during the planning phase to ensure robust production behavior.

Frontend SSR/UX quality gates mandate checking SSR compatibility, hydration quality, progressive enhancement, and user feedback mechanisms during planning. Document how your implementation handles initial render, state synchronization, and user experience across network conditions.

Planning quality gates specify test coverage across simulated offline scenarios, timeout failures, and error handling paths. Include these testing requirements in your planning to ensure comprehensive validation before development.

Deployment safety quality gates ensure planning addresses rollback strategies, feature flags, and monitoring setup upfront. Planning these mechanisms reduces production risk and enables safer feature releases.

Run through all applicable quality gates—network operations, frontend SSR/UX, testing, and deployment safety—documenting decisions for each external dependency, integration point, and risk area before finalizing planning artifacts.