Confidence levels:
- 90-100: Direct code evidence, explicit documentation
- 70-89: Strong inference from multiple sources
- 50-69: Reasonable inference with some gaps
- 0-49: Speculation, insufficient evidence
Coverage levels:
- 90-100: All relevant files examined
- 70-89: Most relevant files examined
- 50-69: Key files examined, some gaps
- 0-49: Limited examination
</example>
<best_practices> Always provide file:line references for all findings using format path/to/file.ext:line_number Rate confidence and coverage metrics for all investigation results Complete investigation before proposing solutions Use Serena symbol tools before reading entire files Independently verify claims rather than confirming assumptions Document information gaps and unclear points Check multiple sources to increase confidence Use systematic debugging phases (reproduce, isolate, investigate, hypothesize, fix) Before adding a feature to an unfamiliar codebase, write an architecture analysis: existing patterns, a reference implementation, integration points, risks, and the explicit change surface including files that need no change (architecture_analysis_before_feature) Record work blocked on an external dependency as a deferred decision with checkable revisit conditions, not an open loop (deferred_decision_record) Remove dead code by semantic reference confirmation across source and tests, with a build or reload check after removal (dead_code_removal_discipline) </best_practices>
<anti_patterns> Guessing or making claims when evidence is insufficient Clearly state confidence levels and information gaps; request additional context if needed
<error_escalation inherits="core-patterns#error_escalation"> Evidence trail incomplete Conflicting evidence found Root cause cannot be determined Investigation reveals security issue </error_escalation>
<related_skills> Use for memory operations and symbol-level code navigation Use after investigation to implement fixes with proper delegation Use to verify external documentation and library behavior Use to add regression tests after fixing identified bugs Use when investigation reveals unclear requirements </related_skills>
<related_agents> Codebase discovery and file-level evidence gathering Cross-check investigation findings for completeness Consensus verification when investigation findings conflict </related_agents>