Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Generate multiple diverse solutions in parallel and select the best.
Install Ensemble Solving
$ npx skills add mhattingpete/claude-skills-marketplace --skill ensemble-solving -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mhattingpete/claude-skills-marketplace ensemble-solving --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mhattingpete/claude-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering-workflow-plugin/skills/ensemble-solving .claude/skills/ensemble-solving && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ensemble-solving" agent skill from https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/ensemble-solving into .claude/skills/ensemble-solving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ensemble-solving", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/ensemble-solvingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mhattingpete/claude-skills-marketplace --skill ensemble-solving -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mhattingpete/claude-skills-marketplace ensemble-solving --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mhattingpete/claude-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering-workflow-plugin/skills/ensemble-solving .agents/skills/ensemble-solving && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ensemble-solving" agent skill from https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/ensemble-solving into .agents/skills/ensemble-solving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ensemble-solving", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mhattingpete/claude-skills-marketplace --skill ensemble-solving -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mhattingpete/claude-skills-marketplace ensemble-solving --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mhattingpete/claude-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering-workflow-plugin/skills/ensemble-solving .cursor/skills/ensemble-solving && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ensemble-solving" agent skill from https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/ensemble-solving into .cursor/skills/ensemble-solving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ensemble-solving", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mhattingpete/claude-skills-marketplace.git --path engineering-workflow-plugin/skills/ensemble-solving--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mhattingpete/claude-skills-marketplace --skill ensemble-solving -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mhattingpete/claude-skills-marketplace ensemble-solving --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mhattingpete/claude-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering-workflow-plugin/skills/ensemble-solving .gemini/skills/ensemble-solving && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ensemble-solving" agent skill from https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/ensemble-solving into .gemini/skills/ensemble-solving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ensemble-solving", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mhattingpete/claude-skills-marketplace ensemble-solvingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mhattingpete/claude-skills-marketplace --skill ensemble-solving -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mhattingpete/claude-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering-workflow-plugin/skills/ensemble-solving .github/skills/ensemble-solving && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ensemble-solving" agent skill from https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/ensemble-solving into .github/skills/ensemble-solving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ensemble-solving", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mhattingpete/claude-skills-marketplace --skill ensemble-solving -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mhattingpete/claude-skills-marketplace ensemble-solving --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mhattingpete/claude-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering-workflow-plugin/skills/ensemble-solving .opencode/skills/ensemble-solving && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ensemble-solving" agent skill from https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/ensemble-solving into .opencode/skills/ensemble-solving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ensemble-solving", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ensemble-solving- GitHub stars
- 680
- Token cost
- ~1.3k tokens
- SKILL.md length
- 439 words
- Files
- 3 (incl. references)
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Generate multiple diverse solutions in parallel and select the best.
- Works in 3 steps: Classify Task Type → Invoke Ensemble Orchestrator → Present Result
- Architecture decisions
- SKILL.md covers When to Use, What It Does, Approach and Diversification Strategies, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ensemble Solving is an agent skill from mhattingpete/claude-skills-marketplace. Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/diversification-strategies.md` and `references/evaluation-rubrics.md`).
It sits in Development. The repository describes itself as: Claude Code Skills for software engineering workflows - Git automation, testing, and code review. The licence is Apache-2.0.
When your agent uses it
- Architecture decisions
- Code generation with multiple valid approaches
- Creative tasks where exploring alternatives improves quality
Example prompts
- “/ensemble-solving”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b5b34bc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ensemble Solving loads about 1.3k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 439 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mhattingpete/claude-skills-marketplace at commit b5b34bc, republished under its Apache-2.0 licence (© mhattingpete). 439 words, ~1,250 tokens.
Download SKILL.mdSave it as
.claude/skills/ensemble-solving/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- ensemble-solving
- description
- Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
Ensemble Problem Solving
Generate multiple solutions in parallel by spawning 3 subagents with different approaches, then evaluate and select the best result.
When to Use
Activation phrases:
- "Give me options for..."
- "What's the best way to..."
- "Explore different approaches..."
- "I want to see alternatives..."
- "Compare approaches for..."
- "Which approach should I use..."
Good candidates:
- Architecture decisions with trade-offs
- Code generation with multiple valid implementations
- API design with different philosophies
- Naming, branding, documentation style
- Refactoring strategies
- Algorithm selection
Skip ensemble for:
- Simple lookups or syntax questions
- Single-cause bug fixes
- File operations, git commands
- Deterministic configuration changes
- Tasks with one obvious solution
What It Does
- Analyzes the task to determine if ensemble approach is valuable
- Generates 3 distinct prompts using appropriate diversification strategy
- Spawns 3 parallel subagents to develop solutions independently
- Evaluates all solutions using weighted criteria
- Returns the best solution with explanation and alternatives summary
Approach
Step 1: Classify Task Type
Determine which category fits:
- Code Generation: Functions, classes, APIs, algorithms
- Architecture/Design: System design, data models, patterns
- Creative: Writing, naming, documentation
Step 2: Invoke Ensemble Orchestrator
Task tool with:
- subagent_type: 'ensemble-orchestrator'
- description: 'Generate and evaluate 3 parallel solutions'
- prompt: [User's original task with full context]The orchestrator handles:
- Prompt diversification
- Parallel execution
- Solution evaluation
- Winner selection
Step 3: Present Result
The orchestrator returns:
- The winning solution (in full)
- Evaluation scores for all 3 approaches
- Why the winner was selected
- When alternatives might be preferred
Diversification Strategies
For Code (Constraint Variation):
| Approach | Focus |
|---|---|
| Simplicity | Minimal code, maximum readability |
| Performance | Efficient, optimized |
| Extensibility | Clean abstractions, easy to extend |
For Architecture (Approach Variation):
| Approach | Focus |
|---|---|
| Top-down | Requirements → Interfaces → Implementation |
| Bottom-up | Primitives → Composition → Structure |
| Lateral | Analogies from other domains |
For Creative (Persona Variation):
| Approach | Focus |
|---|---|
| Expert | Technical precision, authoritative |
| Pragmatic | Ship-focused, practical |
| Innovative | Creative, unconventional |
Show full SKILL.md (163 more words)Show less
Evaluation Rubric
| Criterion | Base Weight | Description |
|---|---|---|
| Correctness | 30% | Solves the problem correctly |
| Completeness | 20% | Addresses all requirements |
| Quality | 20% | How well-crafted |
| Clarity | 15% | How understandable |
| Elegance | 15% | How simple/beautiful |
Weights adjust based on task type.
Example
User: "What's the best way to implement a rate limiter?"
Skill:
- Classifies as Code Generation
- Invokes ensemble-orchestrator
- Three approaches generated:
- Simple: Token bucket with in-memory counter
- Performance: Sliding window with atomic operations
- Extensible: Strategy pattern with pluggable backends
- Evaluation selects extensible approach (score 8.4)
- Returns full implementation with explanation
Output:
## Selected Solution
[Full rate limiter implementation with strategy pattern]
## Why This Solution Won
The extensible approach scored highest (8.4) because it provides
a clean abstraction that works for both simple use cases and
complex distributed scenarios. The strategy pattern allows
swapping Redis/Memcached backends without code changes.
## Alternatives
- **Simple approach**: Best if you just need basic in-memory
limiting and will never scale beyond one process.
- **Performance approach**: Best for high-throughput scenarios
where every microsecond matters.Success Criteria
- 3 genuinely different solutions generated
- Clear evaluation rationale provided
- Winner selected with confidence
- Alternatives summarized with use cases
- User understands trade-offs
Token Cost
~4x overhead vs single attempt. Worth it for:
- High-stakes architecture decisions
- Creative work where first attempt rarely optimal
- Learning scenarios where seeing alternatives is valuable
- Code that will be maintained long-term
Integration
- feature-planning: Can ensemble architecture decisions
- code-auditor: Can ensemble analysis perspectives
- plan-implementer: Executes the winning approach
© mhattingpete, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in engineering-workflow-plugin/skills/ensemble-solving of mhattingpete/claude-skills-marketplace.
- SKILL.md
- references/diversification-strategies.md
- references/evaluation-rubrics.md
Open the folder on GitHubat commit b5b34bc
Compare with similar skills
Ensemble Solving next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ensemble Solving this skillmhattingpete/claude-skills-marketplace | 680 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from mhattingpete/claude-skills-marketplace
All 16 skills in this repoConversation Analyzer
mhattingpete/claude-skills-marketplace
Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement.
Architecture Diagram Creator
mhattingpete/claude-skills-marketplace
Create comprehensive HTML architecture diagrams showing data flows, business objectives, features, technical architecture, and deployment.
Code Transfer
mhattingpete/claude-skills-marketplace
Transfer code between files with line-based precision. An agent skill from mhattingpete/claude-skills-marketplace.
Dashboard Creator
mhattingpete/claude-skills-marketplace
Create HTML dashboards with KPI metric cards, bar/pie/line charts, progress indicators, and data visualizations.
Flowchart Creator
mhattingpete/claude-skills-marketplace
Create HTML flowcharts and process diagrams with decision trees, color-coded stages, arrows, and swimlanes.
Technical Doc Creator
mhattingpete/claude-skills-marketplace
Create HTML technical documentation with code blocks, API workflows, system architecture diagrams, and syntax highlighting.
Related
Categories
Questions about Ensemble Solving
What does Ensemble Solving do?
Generate multiple diverse solutions in parallel and select the best. Ensemble Solving is an agent skill from mhattingpete/claude-skills-marketplace. Generate multiple diverse solutions in parallel and select the best.
When should I use Ensemble Solving?
Ensemble Solving fits situations like: architecture decisions; code generation with multiple valid approaches; creative tasks where exploring alternatives improves quality.
How do I install Ensemble Solving in Claude Code?
Run `npx skills add mhattingpete/claude-skills-marketplace --skill ensemble-solving -a claude-code`. Or copy the skill folder (engineering-workflow-plugin/skills/ensemble-solving in mhattingpete/claude-skills-marketplace) into .claude/skills/ensemble-solving in your project. Claude Code loads it when a task matches its description.
How do I install Ensemble Solving in Codex?
Run `npx skills add mhattingpete/claude-skills-marketplace --skill ensemble-solving -a codex`. Or copy the skill folder (engineering-workflow-plugin/skills/ensemble-solving in mhattingpete/claude-skills-marketplace) into .agents/skills/ensemble-solving in your project. Codex loads it when a task matches its description.
Can I use Ensemble Solving in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mhattingpete/claude-skills-marketplace --skill ensemble-solving -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ensemble-solving, .gemini/skills/ensemble-solving, .github/skills/ensemble-solving and .opencode/skills/ensemble-solving in your project.
What does Ensemble Solving need to run?
SKILL.md names no scripts, command-line tools or credentials: Ensemble Solving is instructions for the agent only.
Does Ensemble Solving access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ensemble Solving safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ensemble Solving use?
Ensemble Solving is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ensemble Solving use?
About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.
What are the alternatives to Ensemble Solving?
Skills that share tags, products or a category with Ensemble Solving: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ensemble Solving?
mhattingpete (a GitHub user) maintains it in mhattingpete/claude-skills-marketplace, which has 680 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on July 25, 2026.
Source: mhattingpete/claude-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.