research

Create read-only research sessions and output ANALYSIS-FILE.md and CONCLUSIONS.md.

Updated May 2, 2026
One-click install
npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill research-tacuchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/Tacuchi/agent-workflow-cli/tree/main/skills/w/roles/research
Command: npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill research-tacuchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides on-demand investigation sessions that read-only inspect the workspace and repositories to gather evidence, then produce ANALYSIS-FILE and CONCLUSIONS, preventing production artifacts from being altered.

Core Features & Use Cases

  • Create a session in the workflow's sessions directory and collect evidence from the workspace using read-only operations (Read, Grep, Glob, MCP queries).
  • Write raw findings to ANALYSIS-FILE.md, synthesize conclusions to CONCLUSIONS.md, and close sessions as closed or inconclusive based on available material.
  • Use across loops (spec-refine-loop, plan-new-loop, plan-exec-loop, quick-loop) to ground decisions with verifiable evidence.

Quick Start

Create a session research for a given question and let the system generate ANALYSIS-FILE.md and CONCLUSIONS.md from the gathered evidence.

Frequently Asked Questions about research

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

FAQPage Schema
How do I conduct read-only code investigation without modifying production artifacts?

On-demand research sessions inspect the workspace using read-only operations like Read, Grep, Glob, and MCP queries to gather evidence. This read-only approach ensures production artifacts remain completely unaltered during the investigation process.

How do I generate structured conclusions from repository workspace evidence?

To generate structured conclusions, the research session writes raw gathered evidence to ANALYSIS-FILE.md and synthesizes findings into CONCLUSIONS.md. Sessions close as either closed or inconclusive based on the verifiable evidence collected from the workspace context.

Can I use automated research sessions across different AI workflow loops?

Automated research sessions apply across spec-refine-loop, plan-new-loop, plan-exec-loop, and quick-loop workflows. The system reads code and MCP data to decide whether to investigate autonomously or prompt the human, grounding workflow decisions with verifiable evidence.

What is the best way to automate evidence collection in a development workspace?

The best way to automate evidence collection is creating an on-demand research session targeting a specific question. The system applies read-only operations to inspect code and MCP data, exporting queries only when needed to preserve production artifacts.

When should I use an automated investigation session instead of manual codebase analysis?

Use an automated investigation session when you need to ground workflow decisions with verifiable evidence across AI loops. It enforces safety rules and prevents accidental modifications, making it safer than manual codebase analysis for producing structured conclusions.