engineering-approach

Enforcing design before coding requires explicit approvals and constraint checks to verify problem understanding before any implementation begins. This approach ensures you document a design and validate the scope before writing code.

Preventing scope creep during complex changes requires rigorous scope-management facilitated by sub-agent orchestration and inline constraint checks. This ensures all modifications stay strictly within the documented spec boundaries.

Sub-agent routing for spec verification works by orchestrating specialized sub-agents and applying inline constraint checks across large specs. This validates that implementations meet design requirements before any task is declared complete.

Yes, an engineering discipline checklist verifies task completion by enforcing mandatory verification steps before declaring work done. It validates that you understood the problem, documented the design, and controlled the scope.

Design review discipline works effectively for large software engineering specs by applying mandatory task discipline and rigorous verification. It orchestrates sub-agents to manage complexity and ensure thorough scope control across changes.