Generated banner for Scientific Problem Selection
Generated logo for Scientific Problem Selection

Scientific Problem Selection

AnthropicOfficialPublished by Anthropic

  • Skill
  • Guidelines
  • Science and research
  • Apache-2.0
  • No issues found

From the author

This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
— the description by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Scientific Problem Selection provides a structured, conversational approach to navigating the research lifecycle. Based on the principles of problem choice over execution quality, this skill helps researchers move from initial ideation to strategic planning. It guides users through nine specific modules—including intuition pumps, risk assessment, and decision tree navigation—to ensure that time is invested in high-impact, feasible problems. By treating research as a series of testable assumptions and strategic decision points, the framework helps scientists avoid common pitfalls, manage adversity, and optimize their research strategy.

What it does

  • Facilitates project ideation using structured intuition pumps.
  • Performs rigorous risk assessment and assumption analysis.
  • Defines success metrics through optimization functions.
  • Navigates complex decision trees for project troubleshooting.
  • Provides strategies for adversity response and problem inversion.
  • Synthesizes research plans into coherent communication packages.

When to use it

  • When choosing a new thesis, postdoc, or lab research direction.
  • When a project is stuck and requires a strategic pivot.
  • When evaluating the feasibility and impact of a new research idea.
  • When planning long-term research strategy or navigating career transitions.
  • When preparing for committee meetings or grant applications.

Advantages

  • Increases research impact by prioritizing problem selection over incremental execution.
  • Reduces time wasted on dead-end projects through early risk identification.
  • Provides a repeatable, evidence-based framework for scientific decision-making.
  • Helps transform crises into opportunities for project growth.
  • Encourages objective evaluation of biological and technical assumptions.

Usage examples

“I have an idea for a new project involving CRISPR, but I am not sure if it is worth pursuing.”
The agent initiates the ideation workflow, asking for a summary and guiding the user through intuition pumps to refine the idea and assess its potential impact.
“My current experiment is failing and I am stuck. Can you help me troubleshoot?”
The agent shifts to the troubleshooting workflow, helping the user identify the core problem, analyze assumptions, and navigate the decision tree to find a path forward.
“I need to evaluate the risks of my proposed research strategy.”
The agent leads the user through a systematic risk assessment, helping to list assumptions, score them by risk level and time-to-test, and identify potential red flags.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/scientific-problem-selection/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip scientific-problem-selection.zip -d .agents/skills

Documentation by Anthropic

Scientific Problem Selection Skills

A conversational framework for systematic scientific problem selection based on Fischbach & Walsh's "Problem choice and decision trees in science and engineering" (Cell, 2024).

Getting Started

Present users with three entry points:

1) Pitch an idea for a new project — to work it up together

2) Share a problem in a current project — to troubleshoot together

3) Ask a strategic question — to navigate the decision tree together

This conversational entry meets scientists where they are and establishes a collaborative tone.


Option 1: Pitch an Idea

Initial Prompt

Ask: "Tell me the short version of your idea (1-2 sentences)."

Response Approach

After the user shares their idea, return a quick summary (no more than one paragraph) demonstrating understanding. Note the general area of research and rephrase the idea in a way that highlights its kernel—showing alignment and readiness to dive into details.

Follow-up Prompt

Then ask for more detail: "Now give me a bit more detail. You might include, however briefly or even say where you are unsure:

  1. What exactly you want to do

  2. How you currently plan to do it

  3. If it works, why will it be a big deal

  4. What you think are the major risks"

Workflow

From there, guide the user through the early stages of problem selection and evaluation:

  • Skill 1: Intuition Pumps - Refine and strengthen the idea

  • Skill 2: Risk Assessment - Identify and manage project risks

  • Skill 3: Optimization Function - Define success metrics

  • Skill 4: Parameter Strategy - Determine what to fix vs. keep flexible

See references/01-intuition-pumps.md, references/02-risk-assessment.md, references/03-optimization-function.md, and references/04-parameter-strategy.md for detailed guidance.


Option 2: Troubleshoot a Problem

Initial Prompt

Ask: "Tell me a short version of your problem (1-2 sentences or whatever is easy)."

Response Approach

After the user shares their problem, return a quick summary (no more than one paragraph) demonstrating understanding. Note the context of the project where the problem occurred and rephrase the problem—highlighting its core essence—so the user knows the situation is understood. Also raise additional questions that seem important to discuss.

Follow-up Prompt

Then ask: "Now give me a bit more detail. You might include, however briefly:

  1. The overall goal of your project (if we have not talked about it before)

  2. What exactly went wrong

  3. Your current ideas for fixing it"

Workflow

From there, guide the user through troubleshooting and decision tree navigation:

  • Skill 5: Decision Tree Navigation - Plan decision points and navigate between execution and strategic thinking

  • Skill 4: Parameter Strategy - Fix one parameter at a time, let others float

  • Skill 6: Adversity Response - Frame problems as opportunities for growth

  • Skill 7: Problem Inversion - Strategies for navigating around obstacles

Always include workarounds that might be useful whether or not the problem can be fixed easily.

See references/05-decision-tree.md, references/06-adversity-planning.md, references/07-problem-inversion.md, and references/04-parameter-strategy.md for detailed guidance.


Option 3: Ask a Strategic Question

Initial Prompt

Ask: "Tell me the short version of your question (1-2 sentences)."

Response Approach

After the user shares their question, return a quick summary (no more than one paragraph) demonstrating understanding. Note the broader context and rephrase the question—highlighting its crux—to confirm alignment with their thinking.

Follow-up Prompt

Then ask: "Now give me a bit more detail. You might include, however briefly:

  1. The setting (i.e., is this about a current or future project)

  2. A bit more detail about what you're thinking"

Workflow

From there, draw on the specific modules from the problem choice framework most appropriate to the question:

  • Skills 1-4 for future project planning (ideation, risk, optimization, parameters)

  • Skills 5-7 for current project navigation (decision trees, adversity, inversion)

  • Skill 8 for communication and synthesis

  • Skill 9 for comprehensive workflow orchestration

See the complete reference materials in the references/ folder.


Core Framework Concepts

The Central Insight

Problem Choice >> Execution Quality

Even brilliant execution of a mediocre problem yields incremental impact. Good execution of an important problem yields substantial impact.

The Time Paradox

Scientists typically spend:

  • Days choosing a problem

  • Years solving it

This imbalance limits impact. These skills help invest more time choosing wisely.

Evaluation Axes

For Evaluating Ideas:

  • X-axis: Likelihood of success

  • Y-axis: Impact if successful

Skills help move ideas rightward (more feasible) and upward (more impactful).

The Risk Paradox
  • Don't avoid risk—befriend it

  • No risk = incremental work

  • But: Multiple miracles = avoid or refine

  • Balance: Understood, quantified, manageable risk

The Parameter Paradox
  • Too many fixed = brittleness

  • Too few fixed = paralysis

  • Sweet spot: Fix ONE meaningful constraint

The Adversity Principle
  • Crises are inevitable (don't be surprised)

  • Crises are opportune (don't waste them)

  • Strategy: Fix problem AND upgrade project simultaneously


The 9 Skills Overview

SkillPurposeOutputTime
1. Intuition PumpsGenerate high-quality research ideasProblem Ideation Document~1 week
2. Risk AssessmentIdentify and manage project risksRisk Assessment Matrix3-5 days
3. Optimization FunctionDefine success metricsImpact Assessment Document2-3 days
4. Parameter StrategyDecide what to fix vs. keep flexibleParameter Strategy Document2-3 days
5. Decision Tree NavigationPlan decision points and altitude danceDecision Tree Map2 days
6. Adversity ResponsePrepare for crises as opportunitiesAdversity Playbook2 days
7. Problem InversionNavigate around obstaclesProblem Inversion Analysis1 day
8. Integration & SynthesisSynthesize into coherent planProject Communication Package3-5 days
9. Meta-FrameworkOrchestrate complete workflowComplete Project Package1-6 weeks

Skill Workflow

SKILL 1: Intuition Pumps
         | (generates idea)
         v
SKILL 2: Risk Assessment
         | (evaluates feasibility)
         v
SKILL 3: Optimization Function
         | (defines success metrics)
         v
SKILL 4: Parameter Strategy
         | (determines flexibility)
         v
SKILL 5: Decision Tree
         | (plans execution and evaluation)
         v
SKILL 6: Adversity Planning
         | (prepares for failure modes)
         v
SKILL 7: Problem Inversion
         | (provides pivot strategies)
         v
SKILL 8: Integration & Communication
         | (synthesizes into coherent plan)
         v
SKILL 9: Meta-Skill
         (orchestrates complete workflow)

Key Design Principles

  1. Conversational Entry - Meet users where they are with three clear starting points

  2. Thoughtful Interaction - Ask clarifying questions; low confidence prompts additional input

  3. Literature Integration - Use PubMed searches at strategic points for validation

  4. Concrete Outputs - Every skill produces tangible 1-2 page documents

  5. Building Specificity - Progressive detail emerges through targeted questions

  6. Flexibility - Skills work independently, sequentially, or iteratively

  7. Scientific Rigor - Claims about generality and feasibility should be evidence-based


Who Should Use These Skills

Graduate Students (Primary Audience)
  • When: Choosing thesis projects, qualifying exams, committee meetings

  • Focus: Skills 1-3 (ideation, risk, impact) + Skill 9 (complete workflow)

  • Timeline: 2-4 weeks for comprehensive planning

Postdocs
  • When: Starting new position, planning independent projects, fellowship applications

  • Focus: All skills, emphasizing independence and risk management

  • Timeline: 1-2 weeks intensive planning

Principal Investigators
  • When: New lab, new direction, mentoring trainees, grant cycles

  • Focus: Skills 1, 3, 4, 6 (ideation, impact, parameters, adversity)

  • Timeline: Ongoing, integrate into lab culture

Startup Founders
  • When: Company inception, pivot decisions, investor pitches

  • Focus: Skills 1-4 (ideation through parameters) + Skill 8 (communication)

  • Timeline: 1-2 weeks for initial planning, revisit quarterly


Reference Materials

Detailed skill documentation is available in the references/ folder:

FileContentSearch Patterns
01-intuition-pumps.mdGenerate research ideasIntuition Pump #, Trap #, Phase [0-9]
02-risk-assessment.mdRisk identificationRisk.*1-5, go/no-go, assumption
03-optimization-function.mdSuccess metricsGenerality.*Learning, optimization, impact
04-parameter-strategy.mdParameter fixationfixed.*float, constraint, parameter
05-decision-tree.mdDecision tree navigationaltitude, Level [0-9], decision
06-adversity-planning.mdAdversity responseadversity, crisis, ensemble
07-problem-inversion.mdProblem inversion strategiesStrategy [0-9], inversion, goal
08-integration-synthesis.mdIntegration and synthesisnarrative, communication, story
09-meta-framework.mdComplete workflowPhase, workflow, orchestrat

Expected Outcomes

Immediate (After Completing Workflow)
  • Clear project vision

  • Honest risk assessment

  • Contingency plans

  • Communication materials ready

  • Confidence in problem choice

6-Month
  • Faster decisions (have framework)

  • Productive adversity handling

  • No existential crises (risks mitigated)

2-Year
  • Published results or strong progress

  • Avoided dead-end projects

  • Career aligned with goals

  • Time well-spent (ultimate measure)


Foundational Reference

Fischbach, M.A., & Walsh, C.T. (2024). "Problem choice and decision trees in science and engineering." Cell, 187, 1828-1833.

Based on course BIOE 395 taught at Stanford University.

Files

references/09-meta-framework.md

SKILL 9: Meta-Framework - Complete Problem Selection Workflow

Overview

This meta-skill orchestrates the complete problem selection process, guiding users through Skills 1-8 in a systematic, iterative way. This skill should be used when comprehensive support is needed from ideation through execution planning, with integrated literature searches and coherent documentation.

When to Use This Skill

Use Skill 9 (Complete Workflow) when:

  • Starting a new project from scratch

  • Major project pivot or reframe needed

  • Grant/fellowship application requiring systematic planning

  • Thesis committee meeting preparation

  • Startup company planning

  • Want comprehensive, documented problem selection process

Use Individual Skills when:

  • You're at a specific stage (e.g., just need risk assessment)

  • Quick consultation on one aspect

  • Updating one component of existing plan

  • Teaching/learning one concept

The Complete Workflow

Overview of the Journey
START: Vague idea or area of interest
    ↓
[SKILL 1] → Problem Ideation Document
    ↓
[SKILL 2] → Risk Assessment Matrix
    ↓
[SKILL 3] → Impact Assessment Document
    ↓
[SKILL 4] → Parameter Strategy Document
    ↓
[SKILL 5] → Decision Tree Map
    ↓
[SKILL 6] → Adversity Playbook
    ↓
[SKILL 7] → Problem Inversion Analysis (if needed)
    ↓
[SKILL 8] → Integrated Project Plan + Communication Materials
    ↓
END: Comprehensive, rigorous project ready to execute

Estimated Time:

  • Intensive: 1 week of focused work (full-time)

  • Distributed: 4-6 weeks with other commitments

  • With iterations: Add 50% more time

You'll invest time once to save years of potential missteps.

Phase-by-Phase Workflow

Phase 1: Preparation (Before Starting)

Gather Your Context:

  1. Your background:

    • Research area/field

    • Current position (grad student, postdoc, PI, etc.)

    • Lab expertise and resources

    • Timeline constraints

  2. Your starting point:

    • Vague area of interest?

    • Specific problem in mind?

    • Must build on existing work?

    • Starting completely fresh?

  3. Your goals:

    • Publication target (journal tier, timeline)?

    • Degree requirement (thesis chapter)?

    • Funding application?

    • Startup foundation?

    • Career development?

Set Expectations:

  • This process will challenge your assumptions

  • You may discover your initial idea needs major revision

  • That's the point—better to know now than after 2 years

  • Intellectual honesty is required; this only works if you're rigorous

Phase 2: Ideation (Skill 1) - ~1 week

What We'll Do:

  1. Understand your context and constraints

  2. Work through relevant intuition pumps

  3. Avoid common ideation traps

  4. Generate 2-3 project ideas

  5. Preliminary literature search to calibrate scope

  6. Select most promising idea

  7. Create Problem Ideation Document (2 pages)

Literature Integration Point 1:

  • Search PubMed for precedents and adjacent work

  • Assess generality of problem

  • Identify methodological advances

  • Determine competition level

Deliverable:

  • Problem Ideation Document with core idea and initial analysis

  • List of 10-15 key papers

  • Preliminary assessment of novelty and feasibility

Checkpoint: Do you have a clear, specific idea that excites you? If not, iterate on intuition pumps.

Phase 3: Risk Analysis (Skill 2) - ~3-5 days

What We'll Do:

  1. Extract ALL assumptions from your idea

  2. Categorize (biological vs. technical)

  3. Score each assumption (risk 1-5, time to test)

  4. Identify high-risk late-reading assumptions

  5. Design go/no-go experiments

  6. Develop mitigation strategies

  7. Create Risk Assessment Matrix (2 pages)

Literature Integration Point 2:

  • Search for technical precedents (has method worked before?)

  • Find biological evidence (what's known about your system?)

  • Identify benchmarks (success rates, effect sizes)

  • Assess timeline realism

Deliverable:

  • Complete assumption analysis table

  • Top 3 high-risk assumptions with mitigation plans

  • Go/no-go experiment designs

  • Revised timeline with decision points

Checkpoint: Is your risk profile acceptable? If risk-5 assumptions are >2 years out, return to Skill 1 to reframe.

Phase 4: Impact Assessment (Skill 3) - ~2-3 days

What We'll Do:

  1. Categorize your project type

  2. Select appropriate optimization function

  3. Score yourself on both axes

  4. Compare to benchmarks

  5. Articulate value system alignment

  6. Develop communication strategy

  7. Create Impact Assessment Document (2 pages)

Literature Integration Point 3:

  • Identify high-impact exemplars in your field

  • Analyze their framing and evaluation

  • Benchmark your potential impact

  • Understand field expectations

Deliverable:

  • Clear optimization function selection

  • Self-assessment on both axes with justification

  • Comparative analysis vs. alternatives

  • Communication strategy for different audiences

Checkpoint: Do you score MEDIUM-HIGH on at least one axis? If not, return to Skill 1 to find higher-impact angle.

Phase 5: Parameter Strategy (Skill 4) - ~2-3 days

What We'll Do:

  1. Inventory all project parameters

  2. Identify which are fixed vs. floating

  3. Assess if you're over/under-constrained

  4. Select strategic fixed parameter

  5. Plan flexibility for contingencies

  6. Create Parameter Strategy Document (2 pages)

Literature Integration Point 4:

  • How did successful projects handle parameters?

  • What parameter choices led to breakthroughs?

  • What over-constraints caused failures?

Deliverable:

  • Complete parameter inventory

  • Strategic rationale for fixed/floating decisions

  • Flexibility matrix for contingencies

  • Project ensemble (family of related projects)

Checkpoint: Have you fixed 1-2 meaningful parameters while maintaining flexibility? If too rigid, adjust.

Phase 6: Decision Tree Planning (Skill 5) - ~2 days

What We'll Do:

  1. Map your project's decision tree

  2. Identify major branch points

  3. Set criteria for each decision

  4. Establish Level 1 / Level 2 rhythm

  5. Create protocols for getting unstuck

  6. Create Decision Tree Map (1-2 pages)

No major literature search here (unless you identify specific decision points needing technical information)

Deliverable:

  • Visual decision tree

  • Decision criteria at each branch

  • Schedule for Level 2 evaluations

  • Protocol for course correction

Checkpoint: Have you planned for regular strategic evaluation, not just execution?

Phase 7: Adversity Preparation (Skill 6) - ~2 days

What We'll Do:

  1. Anticipate likely failure modes

  2. For each, identify upgrade opportunity

  3. Map your project ensemble

  4. Create crisis response protocols

  5. Create Adversity Playbook (2-3 pages)

Literature Integration Point 5:

  • Historical examples of productive pivots

  • How did others capitalize on adversity?

  • What second-generation projects emerged from failures?

Deliverable:

  • Anticipated crisis catalog

  • Upgrade strategies for each

  • Project ensemble map

  • Resilience rituals and protocols

Checkpoint: Are you prepared to see adversity as opportunity? Have you planned how to upgrade, not just fix?

Phase 8: Problem Inversion Toolkit (Skill 7) - ~1 day

What We'll Do:

  1. Review three inversion strategies

  2. Pre-plan applications for your likely obstacles

  3. Create Problem Inversion Analysis (1-2 pages)

This is preparatory - you may not need it now, but when crisis hits, you'll have framework ready.

Deliverable:

  • Strategy 1 application planned

  • Strategy 2 options identified

  • Strategy 3 alternative questions brainstormed

  • Quick-reference guide for crisis

Checkpoint: Do you have concrete strategies for inverting problems when stuck?

Phase 9: Integration and Synthesis (Skill 8) - ~3-5 days

What We'll Do:

  1. Review all outputs from Skills 1-7

  2. Create cohesive narrative

  3. Develop communication materials:

    • 3-slide presentation

    • 1-page summary

    • 1-minute elevator pitch

  4. Write integrated project plan (4-6 pages)

  5. Create living documents for ongoing use

Literature Integration Point 6:

  • Final references for integrated plan

  • Key papers for each section

  • Communication examples from field leaders

Deliverable:

  • Complete Integrated Project Plan (4-6 pages)

  • 3-slide presentation deck

  • 1-page written summary

  • Elevator pitch script

  • Living documents (decision tree, risk matrix, etc.)

Checkpoint: Can you communicate your project compellingly in 1 minute, 5 minutes, and 1 page? Do all pieces fit together coherently?

Iteration and Refinement

When to Iterate

Red Flags That Require Going Back:

From Skill 2 (Risk):

  • Risk-5 assumptions >2 years out → Return to Skill 1 (reframe problem)

  • 3 risk-4-5 assumptions → Return to Skill 1 (simplify or change approach)

From Skill 3 (Impact):

  • Score LOW on both axes → Return to Skill 1 (find higher-impact angle)

  • Optimization function mismatch → Return to Skill 1 (reframe problem)

From Skill 4 (Parameters):

  • 2 fixed parameters → Return to Skill 1 (over-constrained)

  • Zero fixed parameters → Return to Skill 1 (under-constrained)

From Skills 5-6:

  • No clear decision points → Return to Skill 4 (need more flexibility)

  • Every failure mode is existential → Return to Skill 2 (too risky)

Iteration Protocol

Major Revision Needed:

  1. Pause and acknowledge: The process is working—it caught a problem

  2. Return to indicated skill: Usually Skill 1 or 2

  3. Bring forward what you learned: Don't start from scratch

  4. Revised idea → Run through workflow again: Faster the second time

  5. Multiple iterations OK: Better than years on wrong project

Minor Refinement:

  1. Update specific document: E.g., adjust parameter strategy

  2. Check downstream effects: Does this change anything else?

  3. Update integration document: Keep everything coherent

Literature Integration Strategy

Overall PubMed Approach

Throughout the workflow, use PubMed strategically:

  1. Skill 1 (Ideation): Assess generality, find precedents, gauge competition

  2. Skill 2 (Risk): Technical feasibility, biological evidence, benchmarks

  3. Skill 3 (Impact): Field exemplars, evaluation frameworks, benchmarks

  4. Skill 4 (Parameters): Successful parameter choices, cautionary tales

  5. Skill 6 (Adversity): Productive pivots, upgrade examples

  6. Skill 8 (Integration): Communication models, comprehensive references

Search Strategy:

  • Start broad (field overview)

  • Get specific (your exact approach)

  • Look adjacent (related systems/methods)

  • Find benchmarks (what's state-of-art?)

  • Identify competition (who else is doing this?)

Papers to Track:

  • ~10-15 key papers from Skill 1

  • ~5-10 technical papers from Skill 2

  • ~5-10 impact exemplars from Skill 3

  • ~5 parameter lessons from Skill 4

  • ~3-5 pivot examples from Skill 6

  • Total: ~30-50 papers (your foundation)

Final Deliverable Package

What You'll Have at the End

Core Documents (Organized Folder):

  1. 01_Problem_Ideation.pdf (2 pages, Skill 1)

  2. 02_Risk_Assessment.pdf (2 pages, Skill 2)

  3. 03_Impact_Assessment.pdf (2 pages, Skill 3)

  4. 04_Parameter_Strategy.pdf (2 pages, Skill 4)

  5. 05_Decision_Tree.pdf (1-2 pages, Skill 5)

  6. 06_Adversity_Playbook.pdf (2-3 pages, Skill 6)

  7. 07_Problem_Inversion.pdf (1-2 pages, Skill 7)

  8. 08_Integrated_Plan.pdf (4-6 pages, Skill 8)

Communication Materials:

  • Presentation_3slides.pptx

  • Summary_1page.pdf

  • Elevator_Pitch.txt

Living Documents (for ongoing use):

  • Decision_Tree.pdf (update monthly)

  • Risk_Matrix.xlsx (update quarterly)

  • Adversity_Playbook.pdf (consult in crisis)

  • Parameter_Strategy.pdf (revisit if stuck)

Reference Library:

  • Key_Papers.pdf (annotated bibliography, 30-50 papers)

  • Organized by: Ideation / Technical / Impact / Pivots

Total: ~20-25 pages of documentation + supporting materials

Using Your Outputs

For Different Purposes

Grant/Fellowship Applications:

  • Start with Integrated Plan (Skill 8)

  • Include specific aims from Ideation (Skill 1)

  • Show risk mitigation from Risk Assessment (Skill 2)

  • Demonstrate impact from Impact Assessment (Skill 3)

  • Timeline from Decision Tree (Skill 5)

Thesis Committee Meetings:

  • Present 3-slide deck (Skill 8)

  • Walk through decision tree (Skill 5)

  • Discuss risk mitigation (Skill 2)

  • Show parameter flexibility (Skill 4)

  • Demonstrate thoughtful planning

Lab Meetings:

  • Use elevator pitch (Skill 8)

  • Show decision tree updates (Skill 5)

  • Discuss latest adversity and response (Skill 6)

  • Get input on parameter strategy (Skill 4)

Collaborator Conversations:

  • Share 1-page summary (Skill 8)

  • Highlight where their expertise fits (Skill 4)

  • Show risk mitigation plan (Skill 2)

  • Discuss impact potential (Skill 3)

Personal Reflection:

  • Quarterly: Review Decision Tree (Skill 5), update milestones

  • After setbacks: Consult Adversity Playbook (Skill 6)

  • When stuck: Use Problem Inversion (Skill 7)

  • Annual: Full workflow review, consider new projects

Maintenance and Updates

Living Documents Protocol

Monthly:

  • Update Decision Tree (Skill 5)

  • Log adversities and responses (Skill 6)

  • Note new papers or competition

  • Adjust timeline if needed

Quarterly:

  • Review Risk Matrix (Skill 2) - mark assumptions tested

  • Reassess Impact (Skill 3) - has evaluation changed?

  • Check Parameter Strategy (Skill 4) - still optimal?

  • Update Integrated Plan (Skill 8) - keep current

Annually:

  • Complete workflow review

  • Consider new projects with fresh Skill 1 ideation

  • Archive old project docs

  • Extract lessons learned

Success Metrics

How Do You Know This Worked?

Immediate Indicators:

  • Clearer project vision than before

  • Honest assessment of risks

  • Contingency plans for failures

  • Compelling communication materials

  • Alignment between project and values

  • Confidence in problem choice

6-Month Indicators:

  • Major decisions made faster (have framework)

  • Adversity handled productively (used playbook)

  • No existential crises (risks were mitigated)

  • Regular Level 2 evaluation happening

  • Project staying on-track or pivoting smartly

2-Year Indicators:

  • Published results or strong progress

  • Avoided dead-end projects

  • Multiple high-quality options at decision points

  • Skills developed as planned

  • Career trajectory aligned with goals

  • Time well-spent (the ultimate measure)

Key Principles of the Meta-Framework

  1. Systematic > Ad Hoc: Process ensures nothing forgotten

  2. Iterative > Linear: Expect to loop back, that's good

  3. Documented > Mental: Writing forces clarity

  4. Integrated > Fragmented: All skills connect

  5. Living > Static: Update as you learn

  6. Thoughtful > Fast: Time invested now saves years later

  7. Honest > Optimistic: Rigor protects against wishful thinking

  8. Prepared > Surprised: Anticipate adversity

  9. Flexible > Rigid: Parameters float when needed

  10. Passionate > Obligatory: Alignment matters

Getting Started

First Steps

This Week:

  1. Block time in calendar (1-2 hours to start)

  2. Gather your context (background, goals, constraints)

  3. Begin Skill 1 (Intuition Pumps)

  4. Let me know your starting point

This Month:

  1. Work through Skills 1-4 (foundation)

  2. Share with mentor for alignment check

  3. Iterate if major changes needed

  4. Complete Skills 5-8 (execution planning)

This Quarter:

  1. Begin project execution with living documents

  2. Monthly decision tree updates

  3. Quarterly risk assessment reviews

  4. Log adversities and responses

This Year:

  1. Execute planned project

  2. Use frameworks when stuck

  3. Update living documents

  4. Evaluate process and refine

Ready to Begin?

The complete meta-framework is substantial, but each step builds on the last. You'll move through:

  • ~2 weeks of intensive planning

  • Comprehensive documentation

  • Clear decision criteria

  • Communication materials

  • Living documents for ongoing guidance

Most importantly: You'll KNOW you're working on a well-chosen problem with rigorous planning. That confidence is priceless.

Let's start with Skill 1. Are you ready to begin?


Remember: The highest-leverage work in science is choosing the right problem. This meta-framework ensures you spend your finite time wisely. The investment in systematic planning pays dividends for years.

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/knowledge-work-plugins · bio-research/skills/scientific-problem-selection · commit e050c2e
Licence
Apache License 2.0 (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
anthropics/life-sciences

AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download scientific-problem-selection.zip