xiaohongshu
xiaohongshu
investigation-workflow
6-phase investigation workflow for understanding existing systems. Auto-activates for research tasks. Optimized for exploration and understanding, not implementation. Includes parallel agent deployment for efficient deep dives and automatic knowledge capture to prevent repeat investigations.
Full skill instructions
This skill provides a systematic 6-phase workflow for investigating and understanding existing systems, codebases, and architectures. Unlike development workflows optimized for implementation, this workflow is optimized for exploration, understanding, and knowledge capture.
Investigation Tasks (use this workflow):
Development Tasks (use DEFAULT_WORKFLOW.md instead):
Exploration First: Define scope and strategy before diving into code Parallel Deep Dives: Deploy multiple agents simultaneously for efficient information gathering Verification Required: Test understanding through practical application Knowledge Capture: Document findings to prevent repeat investigations
Purpose: Define investigation boundaries and success criteria before any exploration.
Tasks:
Success Criteria:
Deliverables:
Purpose: Plan which agents to deploy and what to investigate, preventing inefficient random exploration.
Tasks:
Agent Selection Guidelines:
Success Criteria:
Deliverables:
Purpose: Deploy multiple exploration agents simultaneously to gather information efficiently.
CRITICAL: This phase uses PARALLEL EXECUTION by default.
Tasks:
[analyzer(module1), analyzer(module2), analyzer(module3)] - Multiple code areas[analyzer, patterns, security] - Multiple perspectives on same area[architect, database, integration] - System architecture explorationParallel Agent Examples:
Investigation: "How does the reflection system work?"
→ [analyzer(.claude/tools/amplihack/hooks/), patterns(reflection), integration(logging)]
Investigation: "Why is CI failing?"
→ [analyzer(ci-config), patterns(ci-failures), integration(github-actions)]
Investigation: "Understand authentication flow"
→ [analyzer(auth-module), security(auth), patterns(auth), integration(external-auth)]
Success Criteria:
Deliverables:
Purpose: Test and validate understanding through practical application.
Tasks:
Verification Examples:
Understanding: "Authentication uses JWT tokens"
Verification: Trace actual token creation and validation in code
Understanding: "CI fails because of dependency conflict"
Verification: Check CI logs, reproduce locally, verify fix works
Understanding: "Reflection analyzes all user messages"
Verification: Examine reflection logs, trace message processing
Success Criteria:
Deliverables:
Purpose: Compile findings into coherent explanation that answers original questions.
Tasks:
Synthesis Outputs:
Success Criteria:
Deliverables:
Purpose: Create durable documentation so this investigation never needs to be repeated.
Tasks:
Documentation Guidelines:
## Discovery: [Brief Title]
**Context**: What was investigated and why
**Key Findings**:
- Main insight 1
- Main insight 2
- **Supporting Evidence**: Links to code, logs, or verification tests
- **Implications**: How this affects the project
- **Related Patterns**: Links to similar patterns in PATTERNS.md
Success Criteria:
Deliverables:
.claude/runtime/logs/After investigation completes, if the task requires implementation (not just understanding), transition to DEFAULT_WORKFLOW.md:
Example Hybrid Workflow:
User: "/ultrathink investigate how authentication works, then add OAuth support"
Phase 1: Investigation
→ Run INVESTIGATION_WORKFLOW.md (6 phases)
→ Complete understanding of existing auth system
→ Document findings in DISCOVERIES.md
Phase 2: Development
→ Transition to DEFAULT_WORKFLOW.md
→ Resume at Step 4 (Research and Design)
→ Use investigation insights to design OAuth integration
→ Continue through Step 15 (implementation → testing → PR)
When to Transition:
Target Efficiency: This workflow targets a 30-40% reduction in message count compared to ad-hoc investigation.
| Ad-Hoc Approach | Investigation Workflow |
|---|---|
| 70-90 messages | 40-60 messages |
| Frequent backtracking | Planned exploration |
| Redundant investigation | Parallel deep dives |
| Unclear scope | Explicit scope definition |
| Lost knowledge | Documented insights |
Efficiency Gains Come From:
Both workflows share core principles:
| Aspect | Investigation Workflow | DEFAULT_WORKFLOW.md |
|---|---|---|
| Goal | Understanding | Implementation |
| Phases | 6 phases | Multi-step workflow |
| Execution | Exploration-first | Implementation-first |
| Parallel Focus | Phase 3 (Deep Dives) | Various steps |
| Testing | Understanding verification | Code validation |
| Deliverable | Documentation | Working code |
| Git Usage | Optional | Required (branches, PRs) |
| Investigation Phase | DEFAULT_WORKFLOW Equivalent | Purpose |
|---|---|---|
| Phase 1: Scope Definition | Step 1: Requirements Clarification | Define what success looks like |
| Phase 2: Exploration Strategy | Step 4: Research and Design | Plan the approach |
| Phase 3: Parallel Deep Dives | Step 5: Implementation | Execute the plan (explore vs. build) |
| Phase 4: Verification | Steps 7-8: Testing | Validate results |
| Phase 5: Synthesis | Step 11: Review | Ensure quality and completeness |
| Phase 6: Knowledge Capture | Step 15: Cleanup | Make results durable |
UltraThink Workflow Detection: When /ultrathink is invoked, it automatically detects investigation tasks using keywords and suggests this workflow.
Automatic Workflow Suggestion:
User: "/ultrathink investigate how authentication works"
UltraThink: Detected investigation task. Using INVESTIGATION_WORKFLOW.md
→ Reading workflow from .claude/workflow/INVESTIGATION_WORKFLOW.md
→ Following 6-phase investigation workflow
→ Starting Phase 1: Scope Definition
To customize this workflow:
.claude/workflow/INVESTIGATION_WORKFLOW.md to modify, add, or remove phasesChanges take effect immediately for future investigations.
Track these metrics to validate workflow effectiveness:
When in doubt about investigation vs. development:
.claude/workflow/INVESTIGATION_WORKFLOW.md (complete 436-line specification).claude/agents/CATALOG.md for all available agents.claude/context/PATTERNS.md for reusable investigation patternsxiaohongshu
technical spec
product ux expert
database patterns
Conduct multi-agent task orchestration and workflow coordination.
Initialize project with Conductor artifacts (product definition,
Expert in web animations, transitions, and motion design using Framer Motion and CSS
Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...
PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.
Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...
Display project status, active tracks, and next actions
Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience