Investigation Workflow FAQs

Question 1

What are Parallel Deep Dives?

Accepted Answer

This is a phase where the workflow deploys multiple specialized agents simultaneously to analyze different modules or perspectives of a system at once, significantly reducing investigation time.

Question 2

How does this differ from the default development workflow?

Accepted Answer

While development workflows focus on implementation and bug fixes, this skill is strictly optimized for exploration, understanding, and knowledge capture without altering functional code.

Question 3

Can I use this for debugging?

Accepted Answer

Yes, it is highly effective for investigating the root cause of complex, non-obvious bugs by verifying hypotheses before transitioning to a fix.

Question 4

When is the best time to trigger the Investigation Workflow?

Accepted Answer

Trigger it whenever you need to answer high-level questions like 'How does the auth system work?' or 'Why is this architecture failing?' before you start writing any code.

Question 5

Does this skill modify my source code?

Accepted Answer

Generally no. Its primary output is documentation and insights. It updates files like DISCOVERIES.md and PATTERNS.md rather than modifying the application logic.

Investigation Workflow

Key Features

Use Cases

Investigation Workflow

Key Features

Use Cases