# Explore Implementation Options in Parallel

Unclear architecture choices can slow build requests and lead to weak decisions. This skill structures brainstorming, parallel variants, scenario testing, and review so teams can compare real implementations.

## Install

```bash
npx skillstore add 2389-research/omakase-off
```

## Metadata

- - Status: approved
- - Slug: 2389-research-omakase-off
- - Version: 1.0.0
- - Author: 2389-research
- - GitHub username: 2389-research
- - License: MIT
- - Repository: https://github.com/2389-research/claude-plugins/tree/main/test-kitchen/skills/omakase-off
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: filesystem, external\_commands
- - Quality score: 70
- - Public page: https://skillstore.pages.dev/skills/2389-research-omakase-off
- - Manifest: https://skillstore.pages.dev/api/skills/2389-research-omakase-off/manifest

## Capabilities

- Offers a choice between guided brainstorming and parallel exploration before detailed implementation.
- Detects architectural indecision during planning and proposes variant exploration.
- Defines a directory structure for shared design notes, variant plans, and final results.
- Coordinates multiple implementation variants through parallel agents or fallback workflows.
- Requires scenario testing, fresh review, and a judge-style comparison before selecting a winner.
- Documents results and cleanup steps after a winning approach is selected.

## Use Cases

- Compare Architecture Choices: Explore options such as storage engines, authentication models, or API styles before committing to one implementation.
- Reduce Planning Deadlock: Move forward when several choices seem plausible by testing real variants instead of debating abstract tradeoffs.
- Evaluate AI Coding Variants: Use scenario tests and review checkpoints to compare outputs from multiple implementation agents.

## Prompt Templates

### Start With A Build Request

```
I want to build a small CLI todo app. Help me choose between brainstorming together and exploring several approaches in parallel.
```

### Explore One Unclear Decision

```
I am not sure whether this feature should use JSON files or SQLite. Use omakase-off to compare the approaches with tests.
```

### Plan Parallel Variants

```
Create parallel implementation plans for two authentication approaches, define shared scenarios, and prepare a comparison workflow.
```

### Judge Completed Variants

```
Review the completed variants, compare scenario results and code review findings, then recommend the winner and cleanup steps.
```

## Limitations

- It is a workflow guide, not an executable automation script.
- It depends on other skills when available and uses fallback behavior when they are absent.
- It can increase repository changes because several variants may be implemented.
- Cleanup commands require careful review to avoid deleting useful branch work.

## Best Practices

- Keep variant count small and focus on the decision with the largest architectural impact.
- Run the same scenario tests against every variant before comparing outcomes.
- Confirm cleanup actions before deleting worktrees or branches.

## Anti Patterns

- Do not explore every possible combination when one primary decision is enough.
- Do not replace scenario testing with manual inspection alone.
- Do not delete losing branches until useful changes have been reviewed.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-27T15:43:13.85\+00:00
- - Summary: Static analysis flagged many external command and weak-crypto patterns, but most are false positives from Markdown backticks, dependency names, and ordinary workflow text. The confirmed risk is operational: the skill instructs agents to create worktrees, write plans, and force-delete loser branches during cleanup. No evidence found of malicious network use, credential access, obfuscation, or prompt injection aimed at bypassing audit rules.

## Stats

- - Views: 175
- - Downloads: 13
- - Favorites: 0
- - Popularity score: 0