feature-investigation

| Mode | Use When | Workflow |

| --------------- | -------------------------------------------- | -------------------------------------------------- |

| Interactive | User available, exploratory question | Real-time collaboration, iterative tracing |

| Autonomous | Deep analysis, complex cross-service tracing | Structured 4-phase workflow with analysis artifact |

1. Discovery - Search codebase for all files related to the feature/question. Prioritize: Entities > Commands/Queries > EventHandlers > Controllers > Consumers > Components.
2. Knowledge Graph - Read and analyze each file. Document purpose, symbols, dependencies, data flow. Batch in groups of 10, update progress after each batch.
3. Flow Mapping - Trace entry points through processing pipeline to exit points. Map data transformations, persistence, side effects, cross-service boundaries.
4. Analysis - Extract business rules, validation logic, authorization, error handling. Document happy path and edge cases.
5. Synthesis - Write executive summary answering the original question. Include key files, patterns used, and text-based flow diagrams.
6. Present - Deliver findings using the structured output format. Offer deeper dives on subtopics.

IMPORTANT: You MUST read these files before starting. Do NOT skip.

• ⚠️ MUST READ .claude/skills/shared/anti-hallucination-protocol.md — Assumption validation, evidence chains, context anchoring
• ⚠️ MUST READ .claude/skills/shared/knowledge-graph-template.md — Per-file analysis structure

If preceded by /scout: Use Scout's numbered file list as analysis targets. Skip redundant discovery. Prioritize HIGH PRIORITY files first.

Brief inline reference:

| Looking for | Search in |

| --------------- | -------------------------------------- |

| Entity CRUD | UseCaseCommands/, UseCaseQueries/ |

| Business logic | Domain/Entities/, *Service.cs |

| Side effects | UseCaseEvents/, *EventHandler.cs |

| Cross-service | Consumer.cs, BusMessage.cs |

| API endpoints | Controllers/, *Controller.cs |

| Frontend | libs/apps-domains/, *.component.ts |

| Background jobs | BackgroundJob.cs, *Job.cs |

⚠️ MUST READ — Full techniques, grep patterns, dependency tracing: references/investigation-techniques.md

Autonomous mode writes analysis to .ai/workspace/analysis/[feature-name]-investigation.md.

⚠️ MUST READ — Full per-file template, knowledge graph fields, findings format: references/evidence-collection.md

```markdown

[Direct answer in 1-2 paragraphs]

1. [Step] - [Explanation with `file:line` reference]

2. [Step] - [Explanation with `file:line` reference]

| File | Purpose |

| ---- | ------- |

[Text diagram: Entry -> Processing -> Persistence -> Side Effects]

• [Subtopic 1]
• [Subtopic 2]

```

• Evidence-based: Every claim needs code evidence. Mark unverified claims as "inferred".
• Question-focused: Tie all findings back to the original question.
• Read-only: Never suggest changes unless explicitly asked.
• Layered explanation: Start simple, offer deeper detail on request.

• feature-implementation - Implementing new features (code changes)
• debugging - Debugging and fixing issues
• scout - Quick codebase discovery (run before investigation)

• Always plan and break many small todo tasks
• Always add a final review todo task to review the works done at the end to find any fix or enhancement needed