agentsclimarketplace

Brainstorming

Skill stevenfackley/opencode-amplifier/.opencode/skills/brainstorming

Contract-governed OpenCode config that amplifies constrained LLMs (Sonnet 4.5, GPT-5.1, cheap corp models) into near-frontier coding agents: multi-agent pipeline with per-agent models, independent test-gen + locked tests, golden-pattern corpus, cross-model review, and an eval harness.

Install
npx -y skills add stevenfackley/opencode-amplifier --skill brainstorming

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use BEFORE any creative or build work — new features, components, behavior changes. Explore intent, requirements, and design with the user before writing a line of code. Prevents a constrained model from confidently building the wrong thing.

SKILL.md

1.3 KB, as published. Nobody here has run it

Brainstorming

Constrained models jump to code fast and commit to the first idea. Don't. The cheapest bug to fix is the one you never build. Run this before implementation.

Process

  1. Restate the goal in your own words and get confirmation. Surface the why, not just the what.
  2. Ask the 2–3 questions that actually change the design — not a survey. Examples: data shape, scale, failure behavior, who/what consumes this, hard constraints.
  3. Propose 1–2 approaches, each with a one-line trade-off. Recommend one. Be decisive.
  4. Name what you'd reuse — existing functions, patterns (PATTERNS.md), libraries — before proposing anything new.
  5. Identify risks/unknowns that should be resolved before or early in the build.
  6. Only after the approach is agreed: hand off to /plan (the architect) for the checklist.

Rules

  • Do not write implementation code during brainstorming.
  • One recommended direction beats five options listed without a recommendation.
  • If the request is ambiguous, the answer is a question, not a guess.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.