plan-output

# Plan Output Skill

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

**Description**: Defines the standard output format for development plans. Ensures plans are layered (TL;DR → Details), include dependency mapping, and remain readable.

## When to Use

Use this skill to format development plans created by the `plan-writer` agent before saving or presenting to user.

## Target Audience

Developers implementing the plan - from junior (who needs details) to senior (who just wants overview).

## Core Principle: Layered Readability

Plans must work at multiple levels:
1. **TL;DR**: Manager/stakeholder can understand in 30 seconds
2. **Approach**: Senior dev can review architecture in 2 minutes
3. **Tasks**: Implementing dev can follow step-by-step
4. **Appendix**: Deep technical details only when needed

## File Naming Convention

Format: `{TASK-ID}-{brief-description}.md` or `{brief-description}.md`

Examples:
- `PROJ-123-add-user-authentication.md`
- `implement-payment-processing.md`
- `GH-456-fix-login-race-condition.md`

## Required Structure

```markdown
# Development Plan: [Task ID] - [Brief Title]

> **Task**: [Link or reference if available]
> **Approach**: [Name of selected approach]
> **Complexity**: S | M | L | XL
> **Created**: [YYYY-MM-DD]

---

## TL;DR

- **What**: [One sentence - what we're building]
- **Why**: [One sentence - why this approach was chosen]
- **How**: [One sentence - key technical decision]
- **Risk**: [One sentence - main risk and mitigation]
- **Scope**: [One sentence - what's explicitly in/out]

---

## Approach

[Maximum 1 page - technical overview]

### Key Decisions

| Decision | Choice | Rationale |
|----------|--------|-----------|
| [Area] | [What we chose] | [Why] |

### Architecture Overview

[Brief description or simple diagram if helpful]

### Dependencies

- **Uses**: [Existing systems this builds on]
- **Affects**: [Systems that may be impacted]
- **External**: [New dependencies introduced]

---

## Tasks

### Phase 1: [Phase Name] (