investigate

Analyze technology stack, codebase structure, technical debt, and DDD readiness.

12|1|Updated Mar 23, 2026

Search Tags:#code analysis #technical debt #system architecture #system investigation #DDD readiness

Ready to run

npx skills add https://github.com/wfukatsu/nexus-architect --skill investigate-wfukatsu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/wfukatsu/nexus-architect/tree/main/skills/investigate
Command: npx skills add https://github.com/wfukatsu/nexus-architect --skill investigate-wfukatsu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables a thorough analysis of a target system's technology stack, codebase structure, technical debt, and domain-driven design (DDD) readiness.

Core Features & Use Cases

Technology Stack Analysis: Identifies languages, frameworks, libraries, and external services.
Codebase Structure: Inspects directory layout, module structure, and entry points.
Technical Debt: Identifies and classifies issues and technical debt.
DDD Readiness: Assesses the system's readiness for DDD migration.
Use Case: Before a major refactor or migration, use this Skill to understand the system's current state and plan for improvements.

Quick Start

Use the /architect:investigate <target_path> command to start the investigation.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I analyze codebase structure and technical debt before a major refactor?▼

To assess DDD readiness for a system migration, you perform a deep-dive system investigation that evaluates the codebase structure and technical debt. This analysis determines how well the current architecture supports domain-driven design principles and highlights areas needing adjustment.

How do I identify the technology stack and external services of an unfamiliar codebase?▼

System investigation identifies technical debt by utilizing AST analysis and pattern searching to detect and classify issues within the codebase. It categorizes these findings into a comprehensive report, highlighting areas that require immediate attention or refactoring.

What is the best way to evaluate a system's readiness for domain-driven design migration?▼

You identify the technology stack and external services by running a system investigation that scans the codebase for languages, frameworks, and libraries. The investigation generates a report detailing all identified technologies and external service integrations.

Can I investigate a codebase for technical debt using AST analysis?▼

To analyze codebase structure and technical debt before a refactor, you need a deep-dive system investigation that inspects directory layout, module structure, and classifies existing issues. This process generates detailed reports to help you understand the current state and plan improvements.

Do I need a local path to start a system architecture investigation?▼

Yes, you need a local path to the codebase to start the system architecture investigation. The analysis requires direct access to the directory to perform AST analysis, pattern searching, and generate multiple detailed investigation reports.