research-findings-writer

# Research Documentation Skill

This skill provides guidelines for creating **research** documentation - investigative findings and discovery results.

## Purpose

Research documentation captures **findings from investigations** - what was discovered, how it was discovered, and what it means. Users consult it to understand past research and build on existing knowledge.

## User Need

> "What did we learn about X?"

## Characteristics

| Attribute | Description |
|-----------|-------------|
| **Orientation** | Discovery |
| **Focus** | Findings and recommendations |
| **Goal** | Capture and share knowledge |
| **Tone** | Objective, analytical |

## Target Directory

Place research documentation in: `docs/research/findings/`

## Writing Guidelines

### DO

- State the research question clearly
- Document methodology transparently
- Provide evidence for each finding
- Include confidence levels
- Acknowledge limitations
- Make actionable recommendations
- Date-stamp for temporal context

### DON'T

- Present opinions as facts
- Skip the methodology section
- Omit limitations or gaps
- Make recommendations without evidence
- Assume findings are permanent (they may become outdated)

## Examples of Good Research Docs

- "Authentication Flow Analysis"
- "Performance Bottleneck Investigation"
- "Third-Party API Capabilities Research"
- "Security Vulnerability Assessment"
- "Technology Comparison Study"

---

## Template

Use this template when documenting research findings:

```markdown
# [Topic] Research

*Research date: [YYYY-MM-DD]*
*Researcher: [Name/Agent]*
*Confidence: [High | Medium | Low]*

## Summary

[2-3 sentences summarizing the key findings]

## Background

[Why this research was conducted - what question were we trying to answer?]

## Methodology

[How the research was conducted]

- [Method 1 - e.g., Code analysis of repository X]
- [Method 2 - e.g., API testing with tool Y]
- [Method 3 - e.g., Documentation review]

## Findings

### Finding 1: [Title]

[Detail