Skip to content

hashgraph-online/awesome-codex-plugins / plugins/boshu2/agentops/skills/idea-genie

idea-genie

Verified

Brainstorm evidence-backed options for what to build, or stress-test an idea. Use when: deciding what to build next, comparing options or testing an idea.

Idea Genie

Return evidence-backed options: every candidate cites an observation, overlap with what already exists is checked before novelty is claimed, and nothing is ranked or picked. That is elicit mode, the entry mode. Duel mode challenges one consequential choice with sealed independent perspectives. Both modes advise; neither selects, schedules, tracks, implements or validates work.

Use insteadWhen
Navigatethe next item in an existing epic or bead graph
Councilmembers scoring each other's ideas, or several views on any question
Premortemhow a plan could fail

Both validators live in this skill's scripts/ directory and need jq; exit 2 means nothing was checked. Then check the fields by hand against the shape and say the validator did not run.

<skill-dir> is the directory that contains this SKILL.md. Claude Code shows it as "Base directory for this skill"; Codex lists this skill's SKILL.md path; in an AgentOps source checkout it is skills/idea-genie. Replace <skill-dir> with that absolute path before running a command. The working directory stays the user's repository. If the host did not show where this skill is installed, use the directory of the SKILL.md you read. If you cannot determine it, do not guess a path or run a same-named script from the current repository; say the bundled script is unavailable and check the fields by hand against the shape, as without jq.

Elicit mode

These rules carry the value:

  1. Observations cite a source: a file and line, issue, doc or measurement. Anything uncited is an assumption, listed apart and never used as support.
  2. Every candidate cites the observations behind it. No cited support, no candidate; an unsupported idea may stay listed as an assumption. Never pad the list to a count.
  3. Check overlap before claiming novelty. Compare each candidate with what the product already does and with earlier decisions that still apply (an ADR, closed issue or recorded lesson). A request an existing capability already covers is not new: record it under overlaps of the candidate it sharpens, or leave it out. Keep an idea a decision rejected only with new evidence that answers its reason, citing the decision under overlaps.
  4. One Given/When/Then per candidate, a normal or edge case whose Then shows the cited problem easing; a Then that could hold while the problem remains aims at a proxy. A goal or a symptom is not yet the problem: cite its cause, or list the cause as an assumption and let the Then show the cited symptom easing.
  5. Do not rank, pick, schedule or start work. The caller or Plan selects.
  6. Stop at saturation. Merge equivalents, and run another pass only while it adds a materially new evidenced candidate. Zero candidates is valid.
  7. Generate before judging. Split the subject into the parts its evidence shows, named in its own words rather than as a directory listing, and draft across each before filtering. Then reshape the predictable first ideas: remove or invert a step, break an assumption treated as fixed, push a constraint to an extreme, borrow how another field solves the same problem, or find a move that makes later moves cheaper. A candidate any project could list unchanged gets a specific observation or is dropped. Keep a one-line reason for each dropped idea in dropped so a later pass does not regenerate it, and list there any part left with no supported candidate.
  8. Behavior outweighs stated interest. "Users asked for it" is weaker than what they do now: the workaround they already use, what it costs them, and observed adoption of anything similar. Name the status quo each candidate must beat in status_quo; if nobody is working around the problem today, say so there.

State the question, constraints, non-goals and sources first. Read only the sources this question needs and cite each one; do not build a merged context store.

Inside a named part (a flow, command, page or stage), go as far as the evidence allows: a candidate that reshapes the wider product is a scope overrun, and one that swaps the subject for another domain replaces it. Drop either with that reason unless a cited observation shows the part cannot change without it. With no named subject, sample each top-level area and the recent commits instead of guessing one focus, and let each candidate's evidence show why its subject deserves attention.

Return the portfolio in this shape:

{
  "schema_version": "idea-portfolio.v1",
  "status": "candidates",
  "observations": [{"claim": "<what is true>", "evidence": "<cited source>"}],
  "assumptions": ["<belief no cited source supports>"],
  "candidates": [{
    "id": "I1",
    "idea": "<short name>",
    "evidence": ["<cited source>"],
    "overlaps": ["<existing capability or decision it extends or repeats>"],
    "status_quo": "<what people do today instead, or none>",
    "scenario": {"given": "<state>", "when": "<event>", "then": "<observable result>"}
  }],
  "dropped": [{"idea": "<short name>", "reason": "<overlap, no evidence, or why it lost>"}]
}

Each candidate evidence entry repeats an observation's evidence exactly. Candidate ids are unique and overlaps may be empty. dropped is optional while there are candidates. When every idea overlaps or lacks support, set status to no-new-work, leave candidates empty and list each idea in dropped with the capability, decision or missing evidence that removed it. observations still needs one entry or more: cite what you read, even when it supports no candidate. The validator rejects any other field, so no rank or winner rides along. For a person, render the same fields as a short list, one block per candidate. Write a file only to a destination the caller names, outside the user's work tree unless the caller asks for a path inside it; with no destination, return the portfolio inline and write no file. Check it with bash "<skill-dir>/scripts/validate-output.sh" <path>, or with - and the JSON on stdin when nothing was written, before returning it to the caller. Elicit worked when the validator accepts the portfolio, each candidate's Then shows its cited problem easing, and no rank or winner appears.

Duel mode

Produce independent challenges for a consequential choice. The result is advisory evidence for Plan: return it to the caller, who may supply it to Plan beside research and operator intent. It never decides whether a plan is ready and never turns a later optional Premortem challenge into an approval gate. Emit no readiness, approval, quorum, retry, budget, helper, delivery, or tracker state: this strategy supplies evidence, not lifecycle authority. Consensus, transport availability or a self-score never becomes readiness.

Door class. Ask what undoing the choice after it lands would cost. A one-way door needs a migration, breaks a published contract or caller, loses data, or has an external effect that cannot be recalled: open the duel workflow, which owns the steps and the idea-challenge.v1 packet. A cheap two-way door is undone by a revert or a flag: run Plan's one fresh challenge instead and return its findings, with no packet, panel, pane manager or model-family rule. Duel mode worked when a one-way door returns a packet that the validator accepts, with every perspective cross-reviewed and dissent kept, and a two-way door returns no packet.

References

finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 319kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 319kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 319kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall