deep-research/skills/research-methodology/SKILL.md
This skill should be used when starting any research task, decomposing a research query, planning research strategy, deciding how many sub-topics to investigate, scaling research effort to query complexity, determining when to stop researching, or dynamically re-planning based on intermediate findings. Covers query analysis, decomposition techniques (Self-Ask, Least-to-Most, DAG-based), effort scaling, plan representations, stopping criteria, and research anti-patterns.
npx skillsauth add oborchers/fractional-cto research-methodologyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Effective research requires deliberate planning before execution. Without decomposition, complex queries overwhelm LLMs — the compositionality gap means models answer sub-questions correctly but fail to compose them into correct multi-hop answers, and this gap does not shrink with model scale alone (Press et al., EMNLP 2023).
Before decomposing, analyze the query along three dimensions:
Complexity classification:
| Level | Characteristics | Example | Approach | |-------|----------------|---------|----------| | Simple | Single fact, one source sufficient | "What is the GAIA benchmark?" | Direct search, no decomposition | | Moderate | 2-4 facets, comparison or analysis | "How does LangGraph compare to CrewAI?" | 2-4 parallel subtopics | | Complex | Multi-faceted, requires synthesis across domains | "How should we architect a deep research agent?" | Full decomposition with dynamic replanning |
Scope narrowing: If a query is vague or overly broad, ask 2-3 clarifying questions before researching. Model this on Claude's desktop deep research flow — refine scope before committing resources.
Questions to consider:
Decomposition strategy should emerge from the query, not from a preset template. The number of subtopics is a function of query complexity, not a fixed constant.
Self-Ask pattern — For multi-hop factual queries. Ask explicit follow-up sub-questions, answer each independently, then compose. Each sub-question becomes a natural insertion point for web search (Press et al., 2023).
Parallel decomposition — For queries with independent facets. Identify subtopics that can be researched simultaneously without dependency. ParallelSearch research shows 12.7% improvement on parallelizable questions using only 69.6% of LLM calls versus sequential approaches (Zhao et al., 2025).
Iterative discovery — For exploratory queries. Start with broad searches, discover subtopics from results, spawn follow-up searches based on what is found. The plan emerges from the research itself.
DAG-based decomposition — For queries with inter-dependent sub-questions. Model decomposition as a directed acyclic graph where some sub-questions depend on answers to others. MindSearch processes 300+ web pages in 3 minutes using this approach (Chen et al., ICLR 2025).
| Query Type | Strategy | Why | |-----------|----------|-----| | "What is X?" | Direct search | Single-hop, no decomposition needed | | "Compare X and Y" | Parallel decomposition | Independent facets, search simultaneously | | "How does X work and what are its implications?" | Iterative discovery | Second part depends on first | | "Comprehensive survey of X" | DAG-based | Multiple inter-dependent threads |
Match research depth to query complexity. Over-researching simple queries wastes tokens; under-researching complex queries produces shallow results.
| Complexity | Workers | Searches per Worker | Total Effort | |-----------|---------|-------------------|--------------| | Simple | 1-2 | 3-5 | Light | | Moderate | 3-4 | 5-10 | Medium | | Complex | 5-8 | 10-20 | Heavy |
The number of workers emerges from decomposition — do not prescribe a fixed count before analyzing the query.
Research plans are hypotheses, not contracts. Re-plan when:
When re-planning, persist the updated plan externally (not just in context) to survive context window truncation.
Combine multiple signals — no single criterion is sufficient:
Stop when at least 3 of these 5 criteria are satisfied.
| Anti-Pattern | Symptom | Fix | |-------------|---------|-----| | Over-decomposition | 15+ subtopics for a moderate query | Let complexity drive decomposition, not ambition | | Under-decomposition | Single monolithic search for a complex query | Analyze facets before searching | | Plan rigidity | Following the original plan despite contradicting evidence | Re-plan when assumptions break | | Circular decomposition | Sub-questions that restate the original question | Each sub-question must be independently answerable | | Premature depth | Deep-diving first subtopic before broad coverage | Breadth-first for initial pass, then depth |
For detailed decomposition techniques and research:
references/decomposition-techniques.md — Self-Ask, Least-to-Most, Plan-and-Solve, DAG-based decomposition with examples and research citationstools
This skill should be used when the user invokes any /plan-* command from the planning-tools plugin (/plan-context, /plan-master, /plan-open-questions, /plan-verify, /plan-tick, /plan-progress, /plan-delete), asks how Claude Code's plan files work, asks where plans are stored, asks to author or audit a multi-phase master planning document, asks how to walk through a plan's Open Questions interactively, asks how to write progress entries, or mentions ~/.claude/plans/ or .claude/planning-tools.local.md. Provides the index of planning-tools commands, the master-plan workflow lifecycle, the v0.3.0+ list-shape mandate (phases and questions as headings + bulleted scope items, never tables), the v0.3.2+ plain-bullet shape (no `- [ ]` checkboxes — heading emoji is the sole tick signal), the progress-entry methodology, and the mechanics of Claude Code's plan-mode file storage.
testing
This skill should be used when the user is adjusting spacing, padding, margins, content density, section gaps, vertical rhythm, or separation between elements. Also applies when reviewing whether a design feels cramped or too sparse, choosing between borders and whitespace for separation, or defining a spacing system. Covers the 4px/8px spacing system, macro vs micro whitespace, content density spectrum, separation techniques (whitespace > background shifts > borders), and vertical rhythm.
development
This skill should be used when the user is defining brand personality in design, choosing between illustration and photography, adding motion or animation, creating visual motifs, ensuring layout variety, customizing CSS framework defaults, or calibrating the level of creative expression for a given context. Covers Lavie & Tractinsky's expressive aesthetics, the expression spectrum (restrained to bold), brand personality translation, illustration systems, photography direction, and template independence.
development
This skill should be used when the user is establishing visual importance, designing headings, creating focal points, designing CTAs or buttons, arranging label-data relationships, implementing scanning patterns (F-pattern, Z-pattern), or ensuring one dominant element per screen. Covers the three levers of hierarchy (size, weight, color), three-tier information architecture, the 'emphasize by de-emphasizing' principle, CTA design, and label-data relationships.