investigate
Investigate Problem
Performs a focused investigation of a specific problem — bug, performance issue, unexpected behavior, or technical challenge — and proposes concrete solutions. Works directly without spec files: understand the problem, dig into the code, and present options.
When to use
Use this skill when the user needs to:
- Understand why something is broken or behaving unexpectedly
- Get solution options for a specific technical problem
- Investigate a bug, error, or performance issue
- Explore approaches to a focused challenge without full spec overhead
Instructions
Step 1: Understand the Problem
If $ARGUMENTS contains a problem description, use it as starting context.
Use the AskUserQuestion tool to clarify:
More from ikatsuba/skills
spec:design
Technical Design - generates architecture diagrams, interfaces, and data flow based on requirements and chosen research solutions. Use when designing how a feature will be built.
18git:amend
Amend Commit - modifies the last commit with staged changes or new message
15spec:requirements
Requirements Analysis - gathers requirements through structured questions and produces a requirements document with testable acceptance criteria. Use when starting a new feature spec or documenting requirements.
14spec:tasks
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
14git:commit
Smart Commit - stages all changes and creates a conventional commit
13spec:do-all
Execute All Tasks - runs all pending tasks from the tasks document, with parallel subtask execution when safe
9