Phase transition validation with artifact checklists, PASS/FAIL/CONDITIONAL gates for workflows
npx skills add https://github.com/vibeeval/vibecosystem --skill gate-check
Faz gecis validasyonu. Bir sonraki faza gecmeden once gerekliliklerin tamam oldugundan emin ol.
Planning ──▶ Development ──▶ Testing ──▶ Staging ──▶ Production
G1 G2 G3 G4 G5
| # | Kriter | Kanit |
|---|--------|-------|
| 1 | Requirements dokumani var | PRD/spec dosyasi |
| 2 | Teknik plan onaylandi | Plan dosyasi + onay |
| 3 | Task'lar olusturuldu | Task listesi |
| 4 | Dependency'ler belirlendi | Dependency listesi |
| 5 | Risk analizi yapildi | Risk matrisi (opsiyonel) |
| # | Kriter | Kanit |
|---|--------|-------|
| 1 | Tum task'lar implement edildi | Task durumlari |
| 2 | Code review tamamlandi | Review onaylari |
| 3 | Build basarili | Build log |
| 4 | Unit test coverage >= 80% | Coverage raporu |
| 5 | Lint/type check temiz | Lint raporu |
| 6 | Security review (auth/data isleri) | Security raporu |
| # | Kriter | Kanit |
|---|--------|-------|
| 1 | Unit testler PASS | Test raporu |
| 2 | Integration testler PASS | Test raporu |
| 3 | E2E critical path testleri PASS | Playwright raporu |
| 4 | Bug'lar triaged (P0/P1 yok) | Bug listesi |
| 5 | Performance baseline karsilandi | Metrikler |
| # | Kriter | Kanit |
|---|--------|-------|
| 1 | Staging'de 24h+ stabil | Monitoring |
| 2 | Smoke testler PASS | Test raporu |
| 3 | Rollback plani hazir | Rollback dokumani |
| 4 | Changelog yazildi | CHANGELOG.md |
| 5 | Stakeholder onay | Onay kaydi |
| Karar | Anlam | Aksiyon |
|-------|-------|---------|
| PASS | Tum kriterler saglanmis | Sonraki faza gec |
| FAIL | Kritik kriter(ler) saglanmamis | Mevcut fazda kal, eksikleri tamamla |
| CONDITIONAL | Minor eksikler var, ilerlenebilir | Sonraki faza gec, eksikleri paralel tamamla |
GATE CHECK: G2 (Development -> Testing)
Date: [tarih]
[PASS] Build basarili
[PASS] Code review tamamlandi
[PASS] Lint/type check temiz
[FAIL] Unit test coverage 72% (min 80%)
[PASS] Security review temiz
[PASS] Tum task'lar implement edildi
KARAR: FAIL
NEDEN: Test coverage yetersiz (72% < 80%)
AKSIYON: Test ekle, %80 ustune cik, gate check'i tekrarla
Projeye ozel gate tanimlamak icin:
### Custom Gate: [Isim]
| # | Kriter | Zorunlu | Kanit |
|---|--------|---------|-------|
| 1 | [Kriter] | Evet/Hayir | [Ne bekleniyor] |
Zorunlu=Evet olan kriterler FAIL'de FAIL, Zorunlu=Hayir olan CONDITIONAL'a duser.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take vibeeval/gate-check from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.