Skills with Subagents

---
name: research
description: >
  Research a topic using three parallel subagents.
  Usage: /research <topic>
  Example: /research "React Server Components"
  Outputs a structured summary covering docs, community, and comparisons.
allowed-tools:
  - Task
  - WebSearch
---

## Role
You are a research coordinator. Delegate subtasks to subagents, then
synthesise their results into one clear report.

## Steps
1. Read the topic the user provides after the command.
2. Spawn three subagents in parallel using the Task tool:
   - Subagent A: Search official documentation and specs.
   - Subagent B: Search community discussions, blog posts, and tutorials.
   - Subagent C: Find comparisons with alternative approaches.
3. Wait for all three subagents to return.
4. Synthesise the results into one report.

## Output format
### Overview
One paragraph summary.

### Key findings
- Bullet per important finding (source: A/B/C)

### Comparisons
Short table if relevant.

### Recommended next step
One sentence.

## Constraints
- Do not add findings that subagents did not return.
- Keep the total output under 600 words.

---
name: audit
description: >
  Audit every TypeScript file in a directory for issues.
  Usage: /audit <directory>
  Example: /audit src/api
  Spawns one subagent per file; collects and ranks all findings.
allowed-tools:
  - Task
  - Read
  - Bash
---

## Context
- Date: $CURRENT_DATE
- Files: $(find ${directory} -name "*.ts" | head -20)

## Steps
1. Read the file list from context.
2. For each file, spawn a subagent with the Task tool:
   - Give the subagent the file path.
   - Ask it to list Critical, Warning, and Suggestion findings.
3. Collect all subagent results.
4. De-duplicate overlapping findings.
5. Rank by severity: Critical first.

## Output format
## Audit — ${directory}
For each file with findings:
  ### filename.ts
  - [Critical]: description
  - [Warning]: description
  - [Suggestion]: description

## Summary
X critical, Y warnings, Z suggestions across N files.