investigation-workflow

Orchestrate a six-phase investigation workflow for analyzing existing systems and capturing knowledge.

2|22|Updated Oct 9, 2025

Search Tags:#architecture #documentation #investigation #agents #parallel #exploration

Ready to run

npx skills add https://github.com/rysweet/azlin --skill investigation-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigation-workflow
Source: https://github.com/rysweet/azlin/tree/main/.claude/skills/investigation-workflow
Command: npx skills add https://github.com/rysweet/azlin --skill investigation-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a formal, six-phase approach to investigate existing systems, enabling efficient exploration, knowledge capture, and concrete outputs.

Core Features & Use Cases

Phase 1: Scope Definition
Phase 2: Exploration Strategy
Phase 3: Parallel Deep Dives
Phase 4: Synthesis and Documentation
Phase 5: Validation and Verification
Phase 6: Knowledge Transfer

Quick Start

Initiate a guided investigation of a system or codebase; the skill will propose a scope and deploy parallel dives.

Frequently Asked Questions about investigation-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I investigate and understand an existing system's architecture?▼

System investigation uses a structured six-phase workflow to explore architecture, dependencies, and behavior. The phases scope the analysis, plan exploration strategy, deploy parallel deep-dives into components, synthesize findings into documentation, validate outputs, and transfer knowledge—enabling efficient understanding of complex systems without scattered notes.

Can I use parallel exploration to diagnose multiple system issues simultaneously?▼

Yes. The workflow deploys parallel agent-driven deep-dives, allowing you to investigate authentication flows, CI failures, and architecture patterns at the same time. Each dive operates independently within a bounded token budget, then results merge into unified documentation and validation.

What's the best way to document system behavior and architecture decisions?▼

The investigation workflow captures findings through automatic knowledge synthesis and documentation in Phase 4, then validates accuracy in Phase 5 before transferring to stakeholders in Phase 6. This ensures documentation stays synchronized with actual system behavior rather than relying on manual notes.

How do I ensure my system exploration stays scoped and doesn't waste tokens?▼

Phase 1 explicitly defines scope and boundaries; each parallel dive operates within a separate, bounded token budget. Explicit triggers and phase-based deliverables prevent scope creep while distributed exploration maximizes efficiency across multiple concurrent investigations.

When should I use a structured investigation workflow versus ad-hoc exploration?▼

Structured investigation works best when you need repeatable outputs, multiple team members exploring simultaneously, explicit documentation of findings, or analysis of complex systems like authentication flows or CI pipelines. Ad-hoc exploration suits quick questions; workflows suit systematic understanding.