agentsclimarketplace

Ultra brainstorming

Skill keithhegit/ultra-orchestration/skills-vnext/ultra-brainstorming

Ultra Orchestration 是一套开源的 AI 工程编排技能体系。它将 OpenSpec 规格主线（Program → Milestone → Change → Slice）与 Ultra-Orchestrator 执行阶段（Intake → Plan → Dispatch → Execute → Review → QA → Deliver → Retro）结合，提升交付稳定性与可审计性。

Install
npx -y skills add keithhegit/ultra-orchestration --skill ultra-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

  • 6 stars6 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

Design-first discovery for Codex Ultra vNext. Use before planning or implementation whenever the request is ambiguous, creative, architecture-sensitive, or likely to span multiple files, workflows, or user-facing behavior. This skill turns a vague idea into an approved spec with one-question-at-a-time clarification, alternative comparison, and an explicit implementation gate.

SKILL.md

2.1 KB, as published. Nobody here has run it

Ultra Brainstorming

Use this skill to create a design-quality front end before planning or coding. This is the main vNext upgrade inspired by obra/superpowers.

Hard Gate

Do not move to planning or implementation until you have:

  1. explored the project context
  2. clarified ambiguities one question at a time when needed
  3. proposed 2-3 approaches with tradeoffs
  4. presented a recommended design
  5. received explicit approval or resolved objections

If the task is truly tiny, compress the design. Do not skip it.

Workflow

  1. Explore the codebase, docs, recent diffs, and any existing specs.
  2. Assess whether the request is one bounded change or several independent subsystems. Decompose if needed.
  3. Ask one clarifying question at a time. Prefer multiple choice when useful.
  4. Propose 2-3 approaches with your recommendation first.
  5. Present the design in sections sized to the complexity.
  6. Write the approved spec artifact.
  7. Self-review for ambiguity, contradiction, and hidden scope creep.
  8. Hand off to ultra-planning.

Preferred Outputs

At minimum produce:

  • problem framing
  • non-goals
  • success criteria
  • constraints
  • proposed architecture or flow
  • testing or verification intent
  • open decisions or assumptions

If the repo uses OpenSpec, write into proposal.md, design.md, and tasks.md under the relevant openspec/changes/<change-id>/ directory.

Quality Bar

  • surface ambiguity instead of silently picking an interpretation
  • prefer the simplest design that satisfies the request
  • avoid speculative abstractions
  • explicitly call out acceptance criteria that downstream planning will need

Read brainstorming-flow and then rely on ultra-vnext-core for the shared contracts.

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.