analyze

Deep Analysis & Investigation

Strip the --delegate flag before passing the prompt to the execution path. </Argument_Routing>

Phase 1 — Create Analysis File

Write CORAL_PROJECT/analysis/{YYYY-MM-DD}-{topic}.md with header:

# Analysis: {topic}

Date: {YYYY-MM-DD}
Question: {user's original request}

• Topic: 2-4 word kebab-case (e.g., auth-flow-gaps, ci-pipeline-root-cause)
• Collision: same date + topic → append -2, -3

Phase 2 — Investigation Steps

For each step in the table below, in order:

1. Evaluate — check "Needed when" against the user's request AND prior findings. Skip if unneeded.
2. Scope — determine target files/modules. Never run unscoped. If a step discovers new facets, carry them into subsequent step evaluation.
3. Execute — run via active mode (see Mode below).
4. Post-process — apply quality gates:
   • Verify CRITICAL/HIGH file:line references (Read cited location, drop incorrect)
   • Drop speculative findings without code evidence. Findings about unchanged code: downgrade and move to ### Peripheral Findings
   • Tag provenance (code trace / test behavior / git history / inference / assumption). Assumption-only → downgrade one level
   • Record finding flow: "N initial → M after gates → K verified [code: X, inference: Y, assumption: Z]"
5. Append — write under the step's output section heading.

Wait for each step's result before evaluating the next. At least one step must run.