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
- Yulivu/debuffer-skillstheir own version, first seen Oct 13, 2026
- yvesory/academic-research-suitetheir own version, first seen Oct 9, 2026
- talhaMah56/claude_skillstheir own version, first seen Sep 12, 2026
- Shri-Phnx/claude-skillstheir own version, first seen Sep 3, 2026
- EarthOnlinePlayer5732/my-skillstheir own version, first seen Aug 11, 2026
- wanshuiyin/Auto-claude-code-research-in-sleeptheir own version, first seen Jul 15, 2026
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.
raja21068Skillresubmit-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
raja21068Skilldeepxiv
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
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- wanshuiyin/Auto-claude-code-research-in-sleep★ 19ksame name
- Chanw-research/claude-code-paper-writing★ 42same name
- EarthOnlinePlayer5732/my-skills★ 17same name
- Yulivu/debuffer-skills★ 9same name
- yvesory/academic-research-suite★ 9same name
- Yusong-Enceladus/claude-skills★ 8same name
- raja21068/AutoResearch★ 2same name
- Shri-Phnx/claude-skills★ 2same name
- talhaMah56/claude_skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- lavishSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- documentation-and-adrsSkill
- electron-secure-boundarySkill
- grill-meSkill
- ipc-contract-designSkill
- ordinus-ui-systemSkill
- provider-runtime-adapterSkill
- shadcn-project-workflowSkill
- sqlite-minimal-persistenceSkill
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
- Distinctive: line 10
Do not create an implementation plan or ADR unless the user explicitly asks for one.
- Distinctive: line 14
Start by restating the idea at a high level and identifying the likely decision being explored.
- Distinctive: line 26
Keep the conversation moving toward a clear decision.
- Distinctive: line 30
Use the areas below when relevant.
- Distinctive: line 35
Test whether the problem is real or only interesting.
- Distinctive: line 41
Check alignment with the current product direction.
- Distinctive: line 42
Look for existing features, docs, workflows, or architecture that already cover the need.
- Distinctive: line 44
Consider whether it fits the current runtime, UI, persistence, IPC, and workflow boundaries.
- Distinctive: line 51
Prefer reversible, observable changes when the problem is not yet proven.
- Distinctive: line 56
Test whether the value is obvious enough to justify product and maintenance cost.
- Distinctive: line 75
After enough exploration, summarize concisely:
“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.
Files
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
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
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.

