Agent skill
test-kitchen
This skill should be used when implementing features with parallel exploration or competition. Triggers on "build", "create", "implement", "try both approaches", "compare implementations". Routes to omakase-off (entry gate for design exploration) or cookoff (exit gate for parallel implementation).
Install this agent skill to your Project
npx add-skill https://github.com/aiskillstore/marketplace/tree/main/skills/2389-research/test-kitchen
SKILL.md
Test Kitchen
Parallel implementation framework with two gate skills:
| Skill | Gate | Trigger |
|---|---|---|
test-kitchen:omakase-off |
Entry | FIRST on any build/create/implement request |
test-kitchen:cookoff |
Exit | At design→implementation transition |
Flow
"Build X" / "Create Y" / "Implement Z"
↓
┌─────────────────────────────────────┐
│ OMAKASE-OFF (entry gate) │
│ Wraps brainstorming │
│ │
│ Choice: │
│ 1. Brainstorm together │
│ 2. Omakase (3-5 parallel designs) │
└─────────────────────────────────────┘
↓
[Brainstorming / Design phase]
↓
Design complete, "let's implement"
↓
┌─────────────────────────────────────┐
│ COOKOFF (exit gate) │
│ Wraps implementation │
│ │
│ Choice: │
│ 1. Cookoff (2-5 parallel agents) │
│ 2. Single subagent │
│ 3. Local implementation │
└─────────────────────────────────────┘
↓
[Implementation]
Key Insight
Skills need aggressive triggers to work. They 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)
When Each Triggers
Omakase-off (Three Triggers)
Trigger 1: BEFORE brainstorming
- "I want to build...", "Create a...", "Implement...", "Add a feature..."
- ANY signal to start building something
- Offers choice: Brainstorm together OR Omakase (parallel designs)
Trigger 2: DURING brainstorming (slot detection)
- 2+ uncertain responses on architectural decisions
- "not sure", "don't know", "either works", "you pick", "no preference"
- Offers to explore detected slots in parallel
Trigger 3: Explicitly requested
- "try both approaches", "explore both", "omakase"
- "implement both variants", "let's see which is better"
Cookoff
- "Let's implement"
- "Looks good, let's build"
- "Ready to code"
- Design doc just committed
- ANY signal to move from design to code
Omakase Mode (Skip Brainstorming)
If user picks "Omakase" at the entry gate:
- Quick context gathering (1-2 questions)
- Generate 3-5 best architectural approaches
- Implement ALL in parallel
- Tests pick the winner
- Skip detailed brainstorming entirely
Best for: "I'm flexible, show me options in working code"
Cookoff Mode (Parallel Implementation)
If user picks "Cookoff" at the exit gate:
- Each agent reads the same design doc
- Each agent creates their OWN implementation plan
- All implement in parallel
- Compare results, pick winner
Best for: "I want to see different implementation approaches"
Key Distinction
| Omakase-off | Cookoff | |
|---|---|---|
| Gate | Entry (before/during brainstorming) | Exit (after design) |
| Question | HOW to explore? | HOW to implement? |
| Parallel on | Different DESIGNS | Same design, different PLANS |
| Triggers | Build request, indecision detection, explicit | "let's implement" signal |
| Skips | Brainstorming (optional via short-circuit) | Nothing - always after design |
Slot Detection (During Brainstorming)
When omakase-off delegates to brainstorming, it passively tracks architectural decisions where user shows uncertainty:
Detection signals:
- "not sure", "don't know", "either works", "both sound good"
- "you pick", "whatever you think", "no preference"
- User defers 2+ decisions in a row
Slot classification:
| Type | Examples | Worth exploring? |
|---|---|---|
| Architectural | Storage engine, framework, auth method | Yes - different code paths |
| Trivial | File location, naming, config format | No - easy to change |
At end of brainstorming:
- If architectural slots exist → offer parallel exploration
- If no slots → hand off to cookoff for implementation
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
perigon-backend
Perigon ASP.NET Core + EF Core + Aspire conventions
perigon-agent
Pointers for Copilot/agents to apply Perigon conventions
perigon-angular
Angular 21+ standalone/Material/signal conventions for Perigon WebApp
fastapi-mastery
Comprehensive FastAPI development skill covering REST API creation, routing, request/response handling, validation, authentication, database integration, middleware, and deployment. Use when working with FastAPI projects, building APIs, implementing CRUD operations, setting up authentication/authorization, integrating databases (SQL/NoSQL), adding middleware, handling WebSockets, or deploying FastAPI applications. Triggered by requests involving .py files with FastAPI code, API endpoint creation, Pydantic models, or FastAPI-specific features.
context7-efficient
Token-efficient library documentation fetcher using Context7 MCP with 86.8% token savings through intelligent shell pipeline filtering. Fetches code examples, API references, and best practices for JavaScript, Python, Go, Rust, and other libraries. Use when users ask about library documentation, need code examples, want API usage patterns, are learning a new framework, need syntax reference, or troubleshooting with library-specific information. Triggers include questions like "Show me React hooks", "How do I use Prisma", "What's the Next.js routing syntax", or any request for library/framework documentation.
browser-use
Browser automation using Playwright MCP. Navigate websites, fill forms, click elements, take screenshots, and extract data. Use when tasks require web browsing, form submission, web scraping, UI testing, or any browser interaction.
Didn't find tool you were looking for?