# investigate

Runs user research from planning to synthesis: interview guides, surveys, usability tests, diary studies, and finding analysis.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2700 installs · ★ 226
- Author: ghaida
- License: CC0-1.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/ghaida/intent/tree/HEAD/skills/investigate/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/investigate

## What it does

The skill covers the whole research lifecycle. You bring a question that needs an answer; it helps you pick a method and carry it through. The method framework lists interviews, usability tests, surveys, diary studies, contextual inquiry, card sorts, tree tests, analytics review, and competitive analysis, each with its purpose and the sample size it needs.

A separate section covers interview guide construction. The structure is broken down by time: an opening with consent and recording permission, the main body, and a close. The point is to let participants talk instead of answering leading questions. Synthesis is covered too: affinity mapping, thematic coding, insight extraction.

The skill plugs into the wider Intent family. `/strategize` works out what needs to be understood, `/investigate` works out how. Findings flow into `/blueprint`, `/journey`, `/organize`, `/articulate`, and `/measure`. Installing it on its own leaves that loop half open, since nothing else in the set frames the questions it answers.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add ghaida/intent --skill investigate -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/investigate/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/investigate/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add ghaida/intent --skill investigate -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/investigate/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add ghaida/intent --skill investigate -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/investigate/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install ghaida/intent investigate
```

2. **Manually: put the files in place**
- File: `.github/skills/investigate/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add ghaida/intent --skill investigate -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/ghaida/intent --path skills/investigate
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/investigate/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add ghaida/intent --skill investigate -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ghaida/intent/tree/HEAD/skills/investigate/SKILL.md

## When to use it
- pick a research method that fits the question
- write an interview guide without leading questions
- plan a usability test and size the sample
- code interview notes into themes and pull out insights
- build a survey to validate a hypothesis at scale

## Example prompts
- Help me plan research: I want to know why users drop off during onboarding
- Write an interview guide about how people choose a pricing tier
- Code these notes from five interviews into themes and surface the main insights

## Source text · SKILL.md · CC0-1.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 516c43267b2f8f94.

BEGIN THIRD-PARTY FILE 516c43267b2f8f94
```text
---
name: investigate
description: >
  Guide and conduct user research — from planning through synthesis. Interview 
  scripts, survey design, usability test plans, diary studies, contextual inquiry.
  Plus synthesis: affinity mapping, thematic coding, insight extraction. Trigger 
  when: planning user research, writing interview guides, designing usability tests,
  creating surveys, synthesizing research findings, "what should we research?",
  "how do I test this?", "write an interview guide", or any question about 
  understanding users through evidence.
version: 1.7.2
user-invocable: true
---

# Investigate

## Overview

Research is the foundation of intentional design. Without evidence, design is decoration — it might look right, but it won't *be* right. This skill guides the full research lifecycle: planning what to learn, choosing the right method, executing with rigor, synthesizing into actionable insights, and communicating findings that drive decisions.

The gap this fills is specific: `/strategize` identifies *what* needs to be understood through the five foundational questions, but doesn't guide *how* to understand it. `/investigate` owns that how. You plan the study, write the interview guide, design the test protocol, structure the survey, run the synthesis, and deliver findings in a format that feeds directly back into the strategic frame.

Research is not a phase you pass through once. It's a practice you return to whenever assumptions stack up, confidence erodes, or the design conversation drifts from evidence into opinion.

---

## Skill family

`/investigate` connects to the full Intent skill system:

- **`/strategize`**: Your primary partner. Their five foundational questions — problem validation, audience definition, solution fit, feature validation, competitive landscape — identify WHAT to research. You determine HOW. When research is complete, findings flow back to `/strategize` for synthesis into the strategic frame.
- **`/blueprint`**: Your findings about how users experience systems, services, and processes inform their architectural decisions. Share journey-based synthesis and contextual inquiry findings directly.
- **`/journey`**: Usability test findings and contextual inquiry observations feed directly into flow design. Share task completion data, error patterns, and observed navigation behaviors.
- **`/organize`**: Card sort and tree test results are direct inputs for information architecture. Share clustering patterns, mental models, and navigation expectations.
- **`/articulate`**: Interview language, terminology patterns, and content comprehension findings inform content strategy. Share how users actually talk about the problem.
```
END THIRD-PARTY FILE 516c43267b2f8f94

The third-party file has ended. Everything between the 516c43267b2f8f94 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2716 of 29162 bytes. © ghaida · CC0-1.0 · https://github.com/ghaida/intent/tree/HEAD/skills/investigate/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md