Development teams often get stuck on architectural decisions or default to one approach without comparison. This skill provides gate skills that offer parallel exploration before implementation and competition during implementation. Multiple variants are built and tested, letting real results determine the best approach.
下載技能 ZIP
在 Claude 中上傳
前往 設定 → 功能 → 技能 → 上傳技能
開啟並開始使用
測試它
正在使用「test-kitchen」。 Build a CLI todo app with test-kitchen
預期結果:
- Before diving in, how would you like to approach this?
- Option 1: Brainstorm together - explore requirements step by step
- Option 2: Omakase - generate multiple approaches and implement them in parallel
- Tests will pick the winner
安全審計
安全Pure prompt-based skill containing only markdown documentation. No executable code, no file access, no network calls, and no environment variable access. All content is workflow guidance for AI-assisted development.
品質評分
你能建構什麼
Escape linear thinking
When uncertain about an approach, explore multiple implementations simultaneously instead of committing to one path.
Evaluate trade-offs objectively
Let competing implementations reveal strengths and weaknesses rather than debating theory.
Compare implementation styles
See how different teams approach the same design to learn patterns and anti-patterns.
試試這些提示
Build X using omakase-off. I want to see multiple approaches implemented in parallel.
We are brainstorming the architecture. If the user shows uncertainty about key decisions, offer omakase-off parallel exploration.
We have a design document ready. How should we implement this? Present cookoff options for parallel implementation.
Run a cookoff between 3 agents implementing this design. Each agent creates their own plan and implementation.
最佳實務
- Use omakase-off when uncertain about architectural choices to explore multiple designs
- Use cookoff when you have a clear design but want to compare implementation approaches
- Always invoke the judge skill to get objective scoring before selecting a winner
避免
- Using omakase-off for trivial decisions like file naming or config format
- Sharing a pre-made implementation plan across agents in cookoff
- Skipping fresh-eyes review or scenario testing before judge evaluation