Technical Investigator

Investigate codebase architecture and implementation details with evidence-based recommendations.

Updated Aug 15, 2023

Search Tags:#architecture #research #analysis #trade-offs #design-decisions

Ready to run

npx skills add https://github.com/connectwithprakash/dotfiles --skill technical-investigator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Technical Investigator
Source: https://github.com/connectwithprakash/dotfiles/tree/main/.claude/skills/technical-investigator
Command: npx skills add https://github.com/connectwithprakash/dotfiles --skill technical-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill systematically investigates technical questions about architecture, design decisions, and implementation patterns to provide reasoned recommendations.

Core Features & Use Cases

Deep code exploration: locate and read relevant implementation details across the codebase.
External research & trade-offs: compare approaches, summarize trade-offs, and cite sources.
Evidence-based recommendations: present options with risks, costs, and benefits.

Quick Start

Ask a technical question about the codebase and request a recommended approach with trade-offs.

Frequently Asked Questions about Technical Investigator

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

FAQPage Schema

How do I investigate why a design decision was made in our codebase?▼

Structured analysis traces implementation details and architecture patterns to uncover design decisions. This Skill systematically explores code, documents trade-offs, and provides evidence-based reasoning for why specific approaches were chosen over alternatives.

What's the best way to understand how a complex feature works across multiple files?▼

Deep code exploration locates and reads relevant implementation details across the codebase to map how components interact. This approach satisfies traceability and evidence-based reasoning by connecting architecture, patterns, and configurations into a coherent picture.

How do I compare different architectural approaches for a new feature?▼

Evidence-based recommendations present multiple options with documented risks, costs, and benefits alongside external research and trade-off analysis. This enables informed decisions grounded in technical reasoning rather than assumptions.

Can I use structured analysis to validate whether our current implementation matches the intended design?▼

Yes. Systematic investigation of architecture and design decisions reveals gaps between documented intent and actual implementation. This identifies misalignments and supports evidence-based recommendations for alignment or refactoring.

When should I conduct a technical investigation before refactoring a module?▼

Before refactoring, investigate the module's design decisions, dependencies, and trade-offs to understand constraints. This prevents breaking hidden assumptions and ensures changes align with the broader architecture and functional requirements.