AGENT SKILL

explore-options

Fan out isolated parallel perspectives on an open-ended decision, then converge on a fit-checked, skimmable shortlist. User-invoked.

License 许可
MIT
所属仓库
adriancodes/skills
最近更新
2026-11-12
Stars
★ 1
Forks
0

01 前言 Front Matter

name
explore-options
license
MIT
metadata
{ "summary": "Fans out isolated parallel frames, converges fit-first with a constraint-checked winner, and renders a 15-line shortlist that expands on demand.", "category": "Design" }
description
Fan out isolated parallel perspectives on an open-ended decision, then converge on a fit-checked, skimmable shortlist. User-invoked.
disable-model-invocation
true

03 SKILL.md 正文

Explore Options

Overview

Obvious answers arrive first. Escape them with isolated parallel branches under distinct frames. Then converge by fit, never cleverness. Branches that see each other anchor, so keep them isolated.

Render the result as a shortlist a skimmer absorbs in one glance. Hold everything else back until asked.

When to Use

  • Explicit invocation only: /explore-options <problem>. Never self-invoke.
  • Fits architecture, API, naming, and product decisions where an obvious answer may be costly.

Do Not Use When

  • One canonical answer exists: give it directly; a fan-out decorates the inevitable.
  • A bug needs a root cause: diagnose (if installed) owns hypothesis generation with a reproduction loop.
  • The deliverable is a module interface: design-an-interface (if installed) produces full competing designs; this skill produces idea-level options.
  • Requirements are unpinned: use create-spec when installed. Otherwise ask one direct question first.

Required Context

  • The problem statement and its stated constraints: scale, latency, budget, compatibility — whatever bounds a viable answer.
  • When constraints are absent, ask exactly one question for constraints and success. Do not fan out first.
  • A harness with parallel subagent dispatch (see Failure Modes when absent).

Workflow

  1. Pick 5 frames. Choose 4 matching tags and exactly 1 wild tag. Vary repeat runs.

    Done when 5 frames are chosen, including one wild frame.

  2. Diverge in parallel. Spawn 5 isolated subagents in one message. Give each only the problem, constraints, frame prompt, and generator instruction. Never serialize them. Never share branch output. Never simulate branches in the orchestrator.

    Done when all 5 branches return.

    Generator instruction, verbatim per branch:

    DIVERGENT mode: generator, not critic. Produce 6 distinct ideas under this frame, one sentence each plus a one-clause rationale. The first three answers any senior engineer would give are banned — push past them. No evaluation, no ranking, no hedging. Return a JSON array only: [{"idea": "...", "why": "..."}]

  3. Converge: fit first. In the orchestrator, no extra agent call:

    • Cluster the pool by underlying angle, never by surface keyword.
    • Rank by fit to the stated problem and viability; novelty breaks ties only.
    • Flag every attractive-but-broken idea as a trap with a one-line reason.
    • Run the constraint check: restate the stated constraints and verify the top pick violates none. A pick that fails is demoted — it never ships as the winner, however clever.
    • Fill the ★ wild slot with the strongest novel-but-viable idea. The wild slot never outranks a constraint-passing pick.

    Done when 3 ranked picks pass and the wild slot is filled or declared empty.

  4. Render the shortlist: 15 lines or fewer. With no preamble or narration, emit exactly, in order:

    • 1 line: the problem and its binding constraint.
    • 3 lines: ranked picks — name, mechanism, why it fits, one line each.
    • 1 line: ★ wild pick, marked as such.
    • Up to 4 lines: traps, one line each with the reason.
    • 1 line: More: "map" for all clusters · "deepen <pick>" for a build sketch.

    No headers, no score chips, no prose between entries. Done when the reply is 15 lines or fewer and every line carries a decision-relevant fact.

  5. Expand on demand only.

    • map: render every cluster — one header line per cluster angle, one line per idea. No commentary.
    • deepen <pick>: call one subagent. Return a 4–8 sentence sketch, key risk, first step, and 3 child ideas.

    Done when the requested layer is rendered and nothing beyond it.

Frames

Pick 5 per run: 4 matching the problem's tags + 1 wild.

Frame Vantage prompt Tags
inversion Ask the opposite question: if the goal is X, how would X be guaranteed to fail? Negate each answer back into an idea. code, design
adversary Attack the obvious solution — exploit it, break it, abuse the legal-but-unintended path. Invert each attack into a design idea. code, design
transplant Pick one distant domain — immune systems, markets, logistics, game design — and force-fit its core mechanism onto this problem literally. wild
extremes Design both ends: the $0, one-hour crudest thing that still does the load-bearing job, and the infinite-budget decade version. The range exposes the middle. code, general
remove the assumption Name the one thing every answer treats as fixed — the framework, the database, request-response itself. Delete it. What becomes possible? code, design, wild
operator at 3am Design so the on-call engineer never gets paged and the auditor can prove what happened. Observability, reversibility, provability first. code, design
beginner A curious 10-year-old who has never seen software: naive, convention-free approaches. Ignore how it is usually done. general, wild
hardware Think in latency budgets, memory layout, physical constraints. Re-ask this as a hardware or systems problem: what do the bus, cache, and clock say? code

Success Criteria

  • The shortlist is 15 lines or fewer and every line carries a decision-relevant fact
  • All 3 ranked picks pass the constraint check against the stated constraints
  • The ★ wild slot holds a viable out-of-playbook idea or is declared empty — it never outranks a constraint-passing pick
  • Branches ran as parallel, isolated subagent calls; nothing was simulated in the orchestrator's context
  • map and deepen layers were rendered only when requested

Common Mistakes

Mistake Fix
Simulating branches sequentially in one context Spawn real parallel subagents; isolation is the mechanism
Clever pick wins over fitting pick Fit and viability rank; novelty breaks ties; the constraint check gates the winner
Rendering the full pool unprompted 15-line shortlist; map and deepen are opt-in layers
Ten variations of one idea presented as breadth Cluster by underlying angle; one cluster means the divergence failed — respawn the weakest 2 frames
"Here are 30 ideas, you decide" Converge with a real ranking; refusing to commit is a cop-out

Failure Modes

  • No parallel subagents: say so. Offer one strong prompt for 10 clustered approaches with traps. Label it anchored, not isolated.
  • All branches converge: report that the problem is narrower than expected. Give the direct answer without padding.
  • No constraints obtainable: stop after one question; rank by viability alone and say the constraint check was skipped.

Provenance

Adapted from ADHD (github.com/UditAkhourii/adhd, MIT). It retains isolation and the generator/critic split. This version adds fit-first ranking, a gated wild slot, and layered output. Cost: about 6 calls, plus 1 per deepen.

Summary

Fan out 5 isolated frames. Converge by fit. Render at most 15 lines. Hold deeper material until requested.

04 同仓库更多 Skills

adriancodes
adriancodes/skills

write-agent-instructions

Make the smallest evidence-backed change to persistent project instructions and test downstream behavior.

★ 1
adriancodes
adriancodes/skills

verify-work

Use when a finished, runnable artifact (a script, config, parser, prompt, or CLI, not a diff under review) must survive hostile input before shipping: the user asks to "verify this script", "find the loopholes", "test this properly against bad input", or asks "is this ready to ship" about one. Also when a shipped artifact failed on an input nobody tried, or when verification so far is a happy-path smoke test.

★ 1
adriancodes
adriancodes/skills

understand-codebase

Use when the user asks to "understand this codebase", "how does this feature work in this repo?", "trace this feature through the code", or needs onboarding, an architecture explanation, or answers about unfamiliar code. Also use for read-only code-path questions before a change.

★ 1
adriancodes
adriancodes/skills

tdd

Use when writing or changing production behavior: implementing a feature, fixing a bug whose cause is already known, or altering stored, transformed, migrated, serialized, or externally transmitted data. Also use when a user says "use TDD", "test first", or "red-green-refactor", and when code is being written before a failing test. For a failure whose cause is unknown, diagnose first.

★ 1
adriancodes
adriancodes/skills

simplify-code

Use when the user asks to "simplify this code", "remove the fluff", or "clean up this over-engineered module", or wants working code that is bloated, duplicated, over-abstracted, or dependency-heavy reduced without changing behavior.

★ 1
adriancodes
adriancodes/skills

review-session

Review an agent session for evidence-backed friction and the smallest measurable remedies.

★ 1