team-attention/tech-decision
skills/tech-decision/SKILL.md
This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use", "tradeoffs", "tech selection", "implementation approach", or needs deep analysis for technical decisions. Provides systematic multi-source research and synthesized recommendations.
$ install --global
skillsauthnpx skillsauth add team-attention/hoyeon tech-decisionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 5:04 AM5.4s3 files scanned
SKILL.md
- name:
- tech-decision
- description:
- This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use", "tradeoffs", "tech selection", "implementation approach", or needs deep analysis for technical decisions. Provides systematic multi-source research and synthesized recommendations.
- version:
- 0.1.0
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:
- Identify Topic: What needs to be decided?
- Identify Options: What are the choices to compare?
- Establish Criteria: What criteria to evaluate by?
- Performance, learning curve, ecosystem, maintainability, cost, etc.
- Set priority based on project characteristics
- See
references/evaluation-criteria.mdfor 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 │
│ → Gather various AI expert perspectives │
│ │
│ 5. [Optional] Context7 MCP │
│ → Query latest docs per library │
└─────────────────────────────────────────────────────────────┘
Phase 3: Synthesis Analysis
Run tradeoff-analyzer agent with gathered information:
- Organize pros/cons per option
- Score by evaluation criteria
- Organize conflicting opinions
- Evaluate reliability (source-based)
Phase 4: Final Report Generation
Generate conclusion-first comprehensive report with decision-synthesizer agent (detailed template: references/report-template.md):
# Technical Decision Report: [Topic]
## Conclusion (Executive Summary)
**Recommendation: [Option X]**
[1-2 sentence key reason]
## Evaluation Criteria and Weights
| Criteria | Weight | Description |
|------|--------|------|
| Performance | 30% | ... |
| Learning Curve | 20% | ... |
## Option Analysis
### Option A: [Name]
**Pros:**
- [Pro 1] (Source: official docs)
- [Pro 2] (Source: Reddit r/webdev)
**Cons:**
- [Con 1] (Source: HN discussion)
**Good fit for:** [Scenario]
## Comprehensive Comparison
| Criteria | Option A | Option B | Option C |
|------|----------|----------|----------|
| Performance | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐⭐ |
| **Total** | **X pts** | **Y pts** | **Z pts** |
## Recommendation Rationale
1. [Key reason 1 with source]
2. [Key reason 2 with source]
## Risks and Considerations
- [Consideration 1]
- [Consideration 2]
Resources Used
Agents (this plugin)
| Agent | Role |
|-------|------|
| codebase-explorer | Analyze existing codebase, identify patterns/constraints |
| docs-researcher | Research official docs, guides, best practices |
| tradeoff-analyzer | Organize pros/cons, comparative analysis |
| decision-synthesizer | Generate conclusion-first final report |
Existing Skills (call via Skill tool)
| Skill | Purpose | How to Call |
|-------|------|-----------|
| dev-scan | Community opinions from Reddit, HN, Dev.to | Skill: dev-scan |
| agent-council | Gather various AI expert perspectives | Skill: agent-council |
Quick Execution Guide
1. Simple Comparison (A vs B)
User: "React vs Vue which is better?"
Execute:
1. Task docs-researcher + Task codebase-explorer (parallel)
2. Skill: dev-scan
3. Task tradeoff-analyzer
4. Task decision-synthesizer
2. Deep Analysis (complex decision)
User: "Thinking about which state management library to use"
Execute:
1. Task codebase-explorer (analyze current state)
2. Parallel:
- Task docs-researcher (Redux, Zustand, Jotai, Recoil, etc.)
- Skill: dev-scan
- Skill: agent-council
3. Task tradeoff-analyzer
4. Task decision-synthesizer
Notes
- Provide Context: More accurate analysis with project characteristics, team size, existing tech stack
- Confirm Criteria: First confirm what criteria matter to user
- Show Reliability: Mark unclear or outdated sources
- Conclusion First: Always present conclusion first
Related Skills
team-attention/verify
development
VerifiedTrustedCommunity
Run a full implementation verification pass after code or data changes. Use when the user asks to verify, QA, smoke test, run checks, validate a feature, inspect a local app in the browser, capture screenshots, or turn discovered QA issues into regression tests/checklists with user approval.
161SKILL.mdUpdated May 22, 2026
team-attention/hoyeon-execute
development
VerifiedTrustedCommunity
Hoyeon execution workflow for Codex. Use when the user invokes "$hoyeon-execute" or wants to execute a Hoyeon plan.json through the Bash-first Codex adapter. This adapter loads the canonical execute skill and follows its Codex runtime surface.
161SKILL.mdUpdated May 16, 2026
team-attention/execute
development
VerifiedTrustedCommunity
Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"
161SKILL.mdUpdated Apr 15, 2026
team-attention/clarify
testing
VerifiedTrustedCommunity
"/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변 기록", "요구사항 명확화", "설계 명확화". Relentless ambiguity-resolution interview that records Q&A under .hoyeon/clarify/<topic>/ and hands off to specify/blueprint/docs when clear.
159SKILL.mdUpdated May 16, 2026