agentleFS
muratgurmuratgur/ordinus/.claude/skills/idea-discovery/SKILL.md

idea-discovery

Skill111 starsChanged 5 months agoMITView on GitHub

Explore a new feature, product idea, technical design, workflow change, or ADR candidate before committing to an implementation plan. Use at the beginning of product or architecture decisions when Codex should challenge assumptions, compare alternatives, inspect relevant docs or code, and help shape a clear recommendation without immediately writing an ADR or implementation plan.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use resubmit-pipeline, deepxiv and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • raja21068Skill

    resubmit-pipeline

    Workflow 5: orchestrate a text-only resubmit of a polished paper to a different venue under hard constraints (no new experiments, no bib edits, no framework changes, never overwrite prior submissions). Phase 0 physical isolation, Phase 0.5 health + anonymity check, Phase 1 audit (proof / claim / citation), Phase 2 microedits via auto-loop with edit-whitelist + citation-audit --soft-only, Phase 3 kill-argument adversarial gate, Phase 4 final compile + Overleaf push via /overleaf-sync. Use when user says \"resubmit pipeline\", \"重投流程\", \"port paper to <new venue>\", \"resubmit to <venue>\", \"tighten paper for resubmission\", or has a rejected/withdrawn paper to move to a different top venue under tight time budget.

    Also in 5 projects that use this

  • raja21068Skill

    deepxiv

    Search and progressively read open-access academic papers through DeepXiv. Use when the user wants layered paper access, section-level reading, trending papers, or DeepXiv-backed literature retrieval.

    Also in 4 projects that use this

  • +10 more from raja21068

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not create an implementation plan or ADR unless the user explicitly asks for one.

    line 10
  2. Distinctive:

    Start by restating the idea at a high level and identifying the likely decision being explored.

    line 14
  3. Distinctive:

    Keep the conversation moving toward a clear decision.

    line 26
  4. Distinctive:

    Use the areas below when relevant.

    line 30
  5. Distinctive:

    Test whether the problem is real or only interesting.

    line 35
  6. Distinctive:

    Check alignment with the current product direction.

    line 41
  7. Distinctive:

    Look for existing features, docs, workflows, or architecture that already cover the need.

    line 42
  8. Distinctive:

    Consider whether it fits the current runtime, UI, persistence, IPC, and workflow boundaries.

    line 44
  9. Distinctive:

    Prefer reversible, observable changes when the problem is not yet proven.

    line 51
  10. Distinctive:

    Test whether the value is obvious enough to justify product and maintenance cost.

    line 56
  11. Distinctive:

    After enough exploration, summarize concisely:

    line 75

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Idea Discovery

Act as a critical thinking partner, not an approval machine. Help the user understand whether an idea is worth pursuing, how it fits the existing product and architecture, and what decision they actually need to make.

Do not create an implementation plan or ADR unless the user explicitly asks for one.

Discovery Loop

Start by restating the idea at a high level and identifying the likely decision being explored.

Then explore the idea step by step using focused questions. Ask one question at a time.

For each question:

  • Explain why the question matters.
  • Provide your recommended answer or direction.
  • Mention meaningful alternatives when relevant.
  • Highlight risks, trade-offs, and hidden assumptions.
  • Inspect existing code, docs, designs, issues, or ADRs when they can answer the question better than the user can.

Keep the conversation moving toward a clear decision. When the idea is vague, help shape it. When the idea is weak, say so clearly and explain why. When several valid paths exist, compare them directly.

Areas To Explore

Use the areas below when relevant. Do not force every area into every conversation.

Problem Clarity

  • Identify the problem being solved.
  • Test whether the problem is real or only interesting.
  • Name who feels the pain and how often.
  • Separate user pain from implementation curiosity.

Fit With Existing Work

  • Check alignment with the current product direction.
  • Look for existing features, docs, workflows, or architecture that already cover the need.
  • Identify whether the idea adds useful structure or unnecessary complexity.
  • Consider whether it fits the current runtime, UI, persistence, IPC, and workflow boundaries.

Alternative Solutions

  • Compare simpler or manual options.
  • Identify what can be postponed.
  • Find the smallest useful version.
  • Prefer reversible, observable changes when the problem is not yet proven.

User And Business Value

  • Name who benefits and what changes for them after the idea exists.
  • Test whether the value is obvious enough to justify product and maintenance cost.
  • Classify the idea as core feature, supporting feature, infrastructure, or distraction.

Technical Direction

  • Identify affected system areas such as data model, IPC contract, UI, runtime, provider adapter, database, or docs.
  • Surface risky technical decisions and integration points.
  • Validate assumptions against existing repository files before asking the user.
  • Separate decisions that must be made now from details that can wait.

Decision Shaping

  • State the actual decision being made.
  • Compare the viable options.
  • Recommend one option and explain why.
  • Capture assumptions and trade-offs that would belong in an ADR if the user later asks for one.

Closing Summary

After enough exploration, summarize concisely:

  • Refined idea
  • Main options considered
  • Recommended direction
  • Key trade-offs
  • Open questions
  • ADR-worthy decisions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.