Test Kitchen

Test Kitchen

Test Kitchen intercepts every build/create/implement request and offers parallel exploration before any code is written. At the design phase, omakase-off offers design exploration (3-5 approaches in parallel). At the implementation phase, cookoff runs parallel implementation competition (2-5 agents each creating their own plan). Tests and the judge pick the winner.

Read more: Cookoff: Same Spec, Different Code · Omakase: Show Me

Parallel implementation framework with two gate skills:

Installation

Flow

Quick examples

Entry gate: omakase-off

When you make a build/create request:

Option 1 (Brainstorm) proceeds to brainstorming skill (or fallback brainstorming), with passive slot detection.

Option 2 (Omakase) does the following:
- Quick context gathering (1-2 questions)
- Generate 3-5 architectural approaches
- Implement ALL in parallel via git worktrees
- Run same scenario tests on each
- Fresh-eyes review survivors
- Present comparison, user picks winner

During brainstorming, slot detection can also trigger it:

Exit gate: cookoff

Option 1 (Cookoff):
- Each agent reads the same design doc
- Each agent creates their OWN implementation plan
- All implement in parallel
- Fresh-eyes review, compare results
- User picks winner

Options 2/3 -- single agent or local implementation proceeds normally.

Why aggressive triggers

Skills can't passively detect "uncertainty" or "readiness" -- they must claim specific moments in the conversation flow.

- Omakase-off claims the BUILD/CREATE moment (before brainstorming)
- Cookoff claims the IMPLEMENT moment (after design)

Dependencies

Test Kitchen orchestrates these skills (falls back gracefully if not installed):

- superpowers:brainstorming
- superpowers:writing-plans
- superpowers:executing-plans
-…