tech-decision

# Tech Decision - Deep Technical Decision Analysis

Skill for systematically analyzing technical decisions and deriving comprehensive conclusions.

## Core Principle

**Conclusion First**: All reports present conclusion first, then provide evidence.

## Use Cases

- Library/framework selection (React vs Vue, Prisma vs TypeORM)
- Architecture pattern decisions (Monolith vs Microservices, REST vs GraphQL)
- Implementation approach selection (Server-side vs Client-side, Polling vs WebSocket)
- Tech stack decisions (language, database, infrastructure, etc.)

## Decision Workflow

### Phase 1: Problem Definition

Clarify decision topic and context:

1. **Identify Topic**: What needs to be decided?
2. **Identify Options**: What are the choices to compare?
3. **Establish Criteria**: What criteria to evaluate by?
   - Performance, learning curve, ecosystem, maintainability, cost, etc.
   - Set priority based on project characteristics
   - See **`references/evaluation-criteria.md`** for detailed criteria

### Phase 2: Parallel Information Gathering

Gather information from multiple sources simultaneously. **Must run in parallel**:

```
┌─────────────────────────────────────────────────────────────┐
│  Run simultaneously (parallel with Task tool)               │
├─────────────────────────────────────────────────────────────┤
│  1. codebase-explorer agent                                 │
│     → Analyze existing codebase, identify patterns/constraints│
│                                                             │
│  2. docs-researcher agent                                   │
│     → Research official docs, guides, best practices        │
│                                                             │
│  3. Skill: dev-scan                                         │
│     → Gather community opinions (Reddit, HN, Dev.to, etc.)  │
│                                                             │
│  4. Skill: agent-council