What is the primary benefit of using Investigate and Plan?

It prevents 'coding in the dark' by ensuring you have a validated, researched plan and architectural agreement before any files are modified.

Does this skill work with external issues?

Yes, it uses the GitHub CLI to fetch comments and details from referenced Issues and Pull Requests to inform the planning process.

How does it validate the final implementation?

It runs repository-specific commands like 'yarn run check' to ensure the codebase remains stable and passes all linting, tests, and build requirements.

Can it search the internet for solutions?

Yes, it utilizes web research tools to find external facts, documentation, or known solutions to similar technical problems across the web.

Why doesn't it write code immediately?

By separating planning from implementation, it allows for a review of assumptions and requirements, significantly reducing errors and technical debt.

Investigative Planning

Name: Investigative Planning
Author: Chronote-gg

byChronote-gg

•

Productivity & Workflow

Researches technical issues and codebase context to generate comprehensive implementation plans before executing code changes.

About

The Investigate and Plan skill streamlines the development lifecycle by enforcing a rigorous pre-coding phase within Claude Code. It leverages both internet research and deep codebase analysis to identify root causes, gather requirements from GitHub issues, and propose concrete changesets. By requiring clarification on assumptions and dependencies before implementation begins, it minimizes rework and ensures that code changes are strategically aligned with project architecture and existing constraints.

Key Features

Dual-source research combining internet searches with deep local codebase analysis
GitHub integration for fetching context directly from referenced issues and pull requests
Comprehensive changeset proposals including file lists, migration needs, and test updates
Strategic clarification loop that blocks implementation until assumptions are validated
Automated post-implementation validation using project-specific check and lint commands
3 GitHub stars

Use Cases

Root-cause analysis for complex production bugs or intermittent incidents
Drafting detailed implementation strategies for new feature requests or product ideas
Assessing the architectural impact of proposed changes in large or unfamiliar codebases

About

Key Features

Dual-source research combining internet searches with deep local codebase analysis
GitHub integration for fetching context directly from referenced issues and pull requests
Comprehensive changeset proposals including file lists, migration needs, and test updates
Strategic clarification loop that blocks implementation until assumptions are validated
Automated post-implementation validation using project-specific check and lint commands
3 GitHub stars

Use Cases

Root-cause analysis for complex production bugs or intermittent incidents
Drafting detailed implementation strategies for new feature requests or product ideas
Assessing the architectural impact of proposed changes in large or unfamiliar codebases