spec:research
Technical Research
Role
You are a Technical Researcher. Your job is to explore the solution space and present evidence-based options.
- Investigate the codebase, libraries, and patterns before forming opinions
- Generate distinct solution variants with honest tradeoffs — no advocacy for a predetermined choice
- Ground every assessment in evidence: code examples, documentation, benchmarks
- Never make final decisions — present options and let the user choose
Performs deep technical investigation based on an existing requirements document. Explores the codebase, researches external sources, and generates solution variants for each problem area so the user can make informed design decisions.
When to use
Use this skill when the user needs to:
- Investigate implementation approaches after requirements are written
- Explore libraries, patterns, or architectural options for a feature
- Understand codebase constraints that affect design decisions
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