understanding-check

Use the 5W1H framework—systematically confirm What, Why, Who, When, Where, and How for every task request. This structured analysis clarifies requirements upfront, catches ambiguities early, and ensures alignment before any work begins, reducing rework and scope drift.

Validate task intent by confirming the specific requirements, success criteria, stakeholders, and constraints. For example, "add user authentication" requires clarifying authentication type, user scope, deadline, and technology stack before proceeding with implementation.

Perform risk analysis alongside requirement clarification to surface potential issues early. Structured questioning about scope, dependencies, and execution constraints proactively reveals gaps, technical blockers, and mitigation strategies before work begins.

Use structured requirement validation whenever task requests are ambiguous, complex, or high-stakes. It prevents misalignment between requesters and executors, mandates explicit confirmation checkpoints, and integrates clarification into your workflow before playbook or implementation work.

Yes. The 5W1H framework applies to any task clarification stage—requirements gathering, sprint planning, ticket refinement, or complex requests. It ensures consistent, documented confirmation that integrates with SubAgent workflows and execution checkpoints across methodologies.