discovery-output

# Discovery Output Skill

**Name**: `dev-plan-v2:discovery-output`

**Description**: Defines the standard format for presenting codebase exploration findings. Designed to summarize existing patterns, dependencies, and risks while assessing if one or multiple approaches are viable.

## When to Use

Use this skill to format the output of the `discovery-agent` before presenting findings to the user or passing to subsequent agents.

## Target Audience

- **Primary**: Other agents in the planning workflow (clarifier, approach-designer, plan-writer)
- **Secondary**: User who wants to understand existing codebase patterns

## Core Principle: Actionable Intelligence

Discovery output should:
1. **Inform decisions** - What exists that affects our approach?
2. **Map dependencies** - What connects to what?
3. **Flag risks** - What could cause problems?
4. **Assess options** - Is there one obvious path or many?

## Required Structure

```markdown
# Discovery Report: [Topic/Task]

> **Explored**: [Brief description of what was searched]
> **Scope**: [Areas of codebase examined]

---

## Existing Patterns

### [Pattern Category 1]

| File | Purpose | Relevance |
|------|---------|-----------|
| `path/to/file.ext` | [What it does] | [How it relates to task] |
| `path/to/another.ext` | [What it does] | [How it relates to task] |

**Pattern Summary**: [1-2 sentences describing the pattern]

### [Pattern Category 2]

[Same structure]

---

## Dependencies

### Direct Dependencies
What the new implementation will use:

- `path/to/service.ext` - [What it provides]
- `path/to/util.ext` - [What it provides]

### Reverse Dependencies
What might be affected by changes:

- `path/to/consumer.ext` - [How it's affected]
- `path/to/other.ext` - [How it's affected]

### External Dependencies
New libraries or services needed:

- [Library/Service] - [Why needed]
- *None identified* (if none)

---

## Risks Identified

| Risk | Type | Severity | Mitigation |
|------|------|----------|------------|