A skill that systematically analyzes technical decision-making and derives comprehensive conclusions.
Core Principles
Conclusion-first deliverables: Every report presents the conclusion first, then provides the rationale.
Usage Scenarios
- 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)
- Technology stack decisions (language, database, infrastructure, etc.)
Decision-Making Workflow
Phase 1: Problem Definition
Clarify the decision topic and context:
- Identify the topic: What needs to be decided?
- Identify options: What are the choices to compare?
- Establish evaluation criteria: By what criteria will they be evaluated?
- Performance, learning curve, ecosystem, maintainability, cost, etc.
- Set criteria priorities suited to the project characteristics
- For detailed criteria, see
references/evaluation-criteria.mdreference
Phase 2: Parallel Information Gathering
Gather information from multiple sources simultaneously. Must be executed in parallel:
┌─────────────────────────────────────────────────────────────┐
│ 동시 실행 (Task tool로 병렬 실행) │
├─────────────────────────────────────────────────────────────┤
│ 1. codebase-explorer agent │
│ → 기존 코드베이스 분석, 현재 패턴/제약사항 파악 │
│ │
│ 2. docs-researcher agent │
│ → 공식 문서, 가이드, best practices 리서치 │
│ │
│ 3. Skill: dev-scan │
│ → 커뮤니티 의견 수집 (Reddit, HN, Dev.to, Lobsters) │
│ │
│ 4. Skill: agent-council │
│ → 다양한 AI 전문가 관점 수집 │
│ │
│ 5. [선택] Context7 MCP │
│ → 라이브러리별 최신 문서 조회 │
└─────────────────────────────────────────────────────────────┘
Execution method:
# Agents는 Task tool로 병렬 실행
Task codebase-explorer: "분석할 주제와 컨텍스트"
Task docs-researcher: "리서치할 기술/라이브러리"
# 기존 스킬은 Skill tool로 호출
Skill: dev-scan (커뮤니티 의견)
Skill: agent-council (전문가 관점)
Phase 3: Comprehensive Analysis
Based on the gathered information, run the tradeoff-analyzer agent:
- Organize pros/cons for each option
- Score by evaluation criteria
- Organize conflicting opinions
- Assess reliability (source-based)
Phase 4: Generate Final Report
Write a conclusion-first comprehensive report with the decision-synthesizer agent (detailed template: references/report-template.md):
# 기술 의사결정 보고서: [주제]
## 결론 (Executive Summary)
**추천: [Option X]**
[1-2문장 핵심 이유]
## 평가 기준 및 가중치
| 기준 | 가중치 | 설명 |
|------|--------|------|
| 성능 | 30% | ... |
| 학습곡선 | 20% | ... |
## 옵션별 분석
### Option A: [이름]
**장점:**
- [장점 1] (출처: 공식 문서)
- [장점 2] (출처: Reddit r/webdev)
**단점:**
- [단점 1] (출처: HN 토론)
**적합한 경우:** [시나리오]
### Option B: [이름]
...
## 종합 비교
| 기준 | Option A | Option B | Option C |
|------|----------|----------|----------|
| 성능 | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐⭐ |
| 학습곡선 | ⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐ |
| **총점** | **X점** | **Y점** | **Z점** |
## 추천 근거
1. [핵심 근거 1 with 출처]
2. [핵심 근거 2 with 출처]
3. [핵심 근거 3 with 출처]
## 리스크 및 주의사항
- [주의점 1]
- [주의점 2]
## 참고 출처
- [출처 목록]
Resources Used
Agents (this plugin)
| Agent | Role |
|---|---|
codebase-explorer |
Analyze existing codebase, identify patterns/constraints |
docs-researcher |
Research official documentation, guides, best practices |
tradeoff-analyzer |
Organize pros/cons per option, comparative analysis |
decision-synthesizer |
Generate conclusion-first final report |
Existing skills (invoked via Skill tool)
| Skill | Purpose | How to invoke |
|---|---|---|
dev-scan |
Community opinions from Reddit, HN, Dev.to, etc. | Skill: dev-scan |
agent-council |
Gather perspectives from various AI experts | Skill: agent-council |
MCP (optional)
- Context7: Look up the latest official documentation for each library
Quick Execution Guide
1. Simple comparison (A vs B)
사용자: "React vs Vue 뭐가 나을까?"
실행:
1. Task docs-researcher + Task codebase-explorer (병렬)
2. Skill: dev-scan
3. Task tradeoff-analyzer
4. Task decision-synthesizer
2. Deep analysis (complex decision-making)
사용자: "우리 프로젝트에 상태관리 라이브러리 뭘 쓸지 고민이야"
실행:
1. Task codebase-explorer (현재 상태 분석)
2. 병렬 실행:
- Task docs-researcher (Redux, Zustand, Jotai, Recoil 등)
- Skill: dev-scan
- Skill: agent-council
3. Task tradeoff-analyzer
4. Task decision-synthesizer
3. Architecture decisions
사용자: "모놀리스 vs 마이크로서비스 어떻게 해야 할까?"
실행:
1. Task codebase-explorer (현재 규모/복잡도 분석)
2. 병렬 실행:
- Task docs-researcher (각 아키텍처 best practices)
- Skill: agent-council (아키텍트 관점)
3. Task tradeoff-analyzer (팀 규모, 배포 복잡도 등 고려)
4. Task decision-synthesizer
Precautions
- Provide context: The more contextual information such as project characteristics, team size, and existing technology stack, the more accurate the analysis can be
- Check evaluation criteria: First confirm what criteria are important to the user
- Indicate reliability: Clearly state information with unclear sources or that is outdated
- Conclusion first: Always present the conclusion first, in a top-down manner
Additional resources
Reference files
references/report-template.md- Detailed report templatereferences/evaluation-criteria.md- Evaluation criteria guide