investigate-and-plan — community investigate-and-plan, Chronote, community, ide skills

v1.0.0

About this Skill

Perfect for Code Review Agents needing advanced investigation and planning capabilities for changesets. Investigate errors, incidents, or product ideas using both internet research and repo-wide codebase research, then propose a concrete changeset plan with clarifying questions before any implementation

Chronote-gg Chronote-gg
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
23
Canonical Locale
en
Detected Body Locale
en

Perfect for Code Review Agents needing advanced investigation and planning capabilities for changesets. Investigate errors, incidents, or product ideas using both internet research and repo-wide codebase research, then propose a concrete changeset plan with clarifying questions before any implementation

Core Value

Empowers agents to streamline the investigation process by researching external sources, inspecting codebase areas, and creating a plan for changesets using GitHub CLI and open clarifying questions.

Ideal Agent Persona

Perfect for Code Review Agents needing advanced investigation and planning capabilities for changesets.

Capabilities Granted for investigate-and-plan

Researching external sources for feature implementation
Inspecting codebase areas for bug fixes
Generating plans for changesets before writing code

! Prerequisites & Limits

  • Requires GitHub CLI access
  • Limited to codebase inspection and planning

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is investigate-and-plan?

Perfect for Code Review Agents needing advanced investigation and planning capabilities for changesets. Investigate errors, incidents, or product ideas using both internet research and repo-wide codebase research, then propose a concrete changeset plan with clarifying questions before any implementation

How do I install investigate-and-plan?

Run the command: npx killer-skills add Chronote-gg/Chronote/investigate-and-plan. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for investigate-and-plan?

Key use cases include: Researching external sources for feature implementation, Inspecting codebase areas for bug fixes, Generating plans for changesets before writing code.

Which IDEs are compatible with investigate-and-plan?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for investigate-and-plan?

Requires GitHub CLI access. Limited to codebase inspection and planning.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Chronote-gg/Chronote/investigate-and-plan. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use investigate-and-plan immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

investigate-and-plan

Install investigate-and-plan, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Investigate And Plan

Overview

Investigate the request, research external sources and the codebase, and produce a plan for a changeset before writing code. Ask open clarifying questions with defaults, then implement only after the plan is agreed.

Workflow

1) Confirm scope and gather context

  • Identify the exact error, feature idea, or decision to investigate.
  • If a PR or Issue is referenced, use the GitHub CLI to fetch details and comments.
  • List the codebase areas to inspect, including backend, frontend, bot, infra, scripts, tests, docs, and configuration.

2) Research

  • Use web.run for internet research, then cite sources for any external facts.
  • Search the codebase broadly with targeted deep dives into relevant subsystems.
  • Capture findings, constraints, and risks, including any existing TODOs or comments.

3) Propose the changeset

  • Provide a concrete plan with files to touch, key edits, data migrations, and test updates.
  • Call out assumptions and viable alternatives.
  • Ask open questions that block implementation, and provide defaults for each question.
  • Do not write code yet.

4) Implement after agreement

  • Wait for the plan to be accepted or adjusted.
  • Implement the agreed changes, keeping the scope aligned to the plan.
  • If new information changes the plan, pause and confirm the update.

5) Validate

  • Run the repo check command, prefer yarn run check unless a no-auto-fix run is required.
  • Ensure tests, build, lint, end-to-end, and complexity or code stats pass as required by the project.
  • Report command outcomes and any remaining gaps.

Related Skills

Looking for an alternative to investigate-and-plan or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer