doncheli/don-cheli-sdd / .agent/skills/doncheli-tech-panel
doncheli-tech-panel
VerifiedConvene a senior engineering expert panel to evaluate technical decisions. Activate when user mentions "tech panel", "technical discussion", "expert opinion", "architecture decision", "which technology", "should we use".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
SKILL.md
View on GitHub---
name: doncheli-tech-panel
description: Convene a senior engineering expert panel to evaluate technical decisions. Activate when user mentions "tech panel", "technical discussion", "expert opinion", "architecture decision", "which technology", "should we use".
---
# Don Cheli: Senior Tech Panel
## Panel Members
Each expert has 15+ years of experience and must back every argument with a real-world incident, benchmark, or published case study:
| Expert | Domain |
|---------------------|----------------------------------------------------|
| Tech Lead | Code quality, team velocity, maintainability |
| Sr. Backend Engineer| API design, DB performance, concurrency, latency |
| Sr. Frontend Engineer| Bundle size, rendering performance, DX, a11y |
| Software Architect | System design, scalability, coupling, data flows |
| DevOps / SRE | Operability, deployability, observability, cost |
## Instructions
1. Read the technical question or architecture decision to evaluate
2. Each panelist states their position with:
- A clear recommendation (yes/no/conditional/alternative)
- At least one supporting data point (incident, benchmark, RFC, published postmortem)
- One concern or caveat
3. Panelists interact: if two panelists disagree, they must address each other's arguments directly
4. Conclude with a panel consensus or a documented dissent
## Output Format
```
## Tech Panel: <topic>
### Tech Lead
**Position:** …
**Evidence:** …
**Concern:** …
### Sr. Backend Engineer
**Position:** …
**Evidence:** …
**Concern:** …
### Sr. Frontend Engineer
**Position:** …
**Evidence:** …
**Concern:** …
### Software Architect
**Position:** …
**Evidence:** …
**Concern:** …
### DevOps / SRE
**Position:** …
**Evidence:** …
**Concern:** …
### Cross-Debate
<Panelist A> → <Panelist B>: …
…
### Panel Conclusion
**Consensus / Majority recommendation:** …
**Dissent (if any):** …
**Conditions for the recommendation:** …
```
## Quality Gate
- Every panelist must cite at least one real-world data point — no opinions without evidence
- If a panelist's domain is not directly relevant to the question, they must explain why they still have a stake
- Consensus requires ≥3/5 panelists; otherwise output DISSENT with open questions
## Do not use this skill when
- The decision is purely business/product (use doncheli-debate instead)
- The question has a clear industry standard answer (just cite the standard)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |