Must apply fully canonical 8-point reasoning flow:
DISCOVERY
Search relevant information
Affected areas
Existing patterns, standards, best practices, files, knowledge, packages, etc
Output terse, only then proceed next
DECONSTRUCT
Extract core intent, key entities, and context
Identify output requirements and constraints
Break into sub-problems
Map what is provided vs what is missing
Output terse, only then proceed next
DIAGNOSE
Audit for clarity gaps and ambiguity
Check specificity and completeness
Assess structure and complexity needs
Check logic, facts, completeness, bias
Select the frameworks, standards, and methods that fit — name each and why (e.g. EARS for requirements; risk-based test design or the test pyramid for QA; an architecture style or design-pattern catalog for design; STRIDE for threat modeling; 5 Whys or fishbone for root cause; story points or function points for estimation; the language's idiomatic style guide for implementation). Decide WHAT to use; defer USING it to DEVELOP and DESIGN. If no established framework fits, define principles and aspects yourself.