Analyze

Recommend the smallest adequate design, method and check strategy from inspected evidence. Ordinary requests and bounded handoffs use this procedure. The technical lead selects routine engineering choices; in standalone use that is the caller, without spawning an agent or asking the maintainer to choose techniques.

Prerequisites and companions

Check applicable project instructions and agreement once per context, reusing guidance already read. Follow relevant context/authority and directory/runtime pointers; compare decision/effect authority, safety, verification, documentation and continuation responsibilities with this task. Equivalent existing layouts need no Setup provenance or template. Identify absent, conflicting or unverifiable guidance and recommend explicit setup/reconciliation without starting it or rewriting policy. Missing common guidance blocks dependent project analysis; missing tracker/model/domain detail blocks only that capability. Continue authorized inspection and conversation returns where supported.

Discover companions through runtime/project catalogs or approved locations, not assumed siblings. Read complete entries and required references; recover truncated reads before dependent work and resolve links from their containing source. For a conditional library, inspect the documented pointer and read the complete relevant library without invoking its unrelated procedure. Record source/revision or digest and semantic compatibility; ambiguity blocks that route. Recheck changed sources/task/authority. Missing helpers grant no installation or legacy fallback.

• Use research only for unresolved source/API/version questions; require cited applicable findings, uncertainty and freshness.
• For actual meaning/model changes or potentially qualifying enduring decisions, read domain handoff. Reading unchanged definitions needs no invocation. Domain writes require authorized deltas; ADRs need explicit agreement and permission.
• Before optional delegation, establish actual permission and read delegation. Otherwise analyze directly; no worker or model assessment is required.
• Inspect method capabilities in step 4; missing packages do not invalidate supported recommendations.

1. Bound the question

Identify scope, deciding questions, acceptance/confirmed decisions, exclusions, limitations, authority, protected state and a finite inspection bound from the request or caller evidence. Keep commitments traceable; no mandatory form or spec hierarchy. Assess proposals as proposed. Return missing commitments to their owner with consequences and a recommendation; continue unaffected inspection.