Experienced Developer Investigation

Investigate codebase tasks to quantify scope and create implementation plans.

2|1|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/ClementWalter/rookie-marketplace --skill experienced-developer-investigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Experienced Developer Investigation
Source: https://github.com/ClementWalter/rookie-marketplace/tree/main/chief-of-staff/skills/experienced-dev
Command: npx skills add https://github.com/ClementWalter/rookie-marketplace --skill experienced-developer-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides experienced developers through thorough problem investigation, scope quantification, risk identification, and the creation of a detailed implementation plan that a junior can execute reliably.

Core Features & Use Cases

  • Investigation & context: Gather context, identify scope, and document constraints.
  • Scope quantification: Produce a clear impact assessment and a break-down plan with tasks and estimates.
  • Implementation plan: Deliver a step-by-step plan suitable for a junior developer to implement.

Quick Start

Generate an Investigation Report outlining the current state, required changes, and a concrete step-by-step plan for execution.

Frequently Asked Questions about Experienced Developer Investigation

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

FAQPage Schema
How do I create a detailed implementation plan before coding?

An implementation plan breaks down a task into concrete steps by investigating scope, identifying dependencies, and estimating effort. Gather context about the codebase, document constraints, quantify the impact, and produce a step-by-step guide that junior developers can follow reliably.

What's the best way to estimate story points for a development task?

Story point estimation uses poker planning to quantify effort across a team. Investigate the task scope, identify risks and dependencies, then apply relative sizing to align estimates with actual complexity and workload.

How do I investigate a codebase task to identify scope and risks?

Task investigation gathers context, documents current state and required changes, identifies dependencies and constraints, and flags risks. This structured analysis produces a clear impact assessment and breakdown that guides implementation.

Can I use this approach to guide junior developers through implementation?

Yes. A detailed implementation plan with step-by-step instructions, risk identification, and effort estimates enables junior developers to execute complex tasks independently and reliably across diverse project contexts.

What documentation should I create during task planning?

Thorough task planning produces an investigation report covering current state, required changes, scope quantification, dependency mapping, risk analysis, effort estimates, and a concrete step-by-step execution plan.