plan-research

Decompose a research topic into a structured JSON plan with MECE sub-questions.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill plan-research-jin9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-research
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/plan-research
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill plan-research-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a vague research topic into a rigorous, actionable plan is hard: sub-questions overlap, scope drifts, and downstream search or writing stages lack a clear contract. This Skill converts a raw topic into a structured JSON research plan that later workflow stages can execute against without asking the user anything further. ## Core Features & Use Cases - Structured Plan Generation: Produces a thesis question, 3–10 MECE sub-questions, coverage dimensions, out-of-scope exclusions, and success criteria as a single JSON object. - Depth and Audience Dials: Adjusts sub-question count and phrasing based on quick/standard/deep depth and general/technical/executive audiences. - Failure Handling: Emits an explicit plan_skipped failure shape when the topic is empty or unintelligible, so downstream stages stop cleanly. - Use Case: As stage 1 of a multi-stage researcher workflow, feed it "Vector databases for RAG" at standard depth and receive a five-question plan that search, extraction, synthesis, and review stages consume directly. ## Quick Start Ask the agent to plan research on your chosen topic, optionally specifying a depth level and target audience.

Frequently Asked Questions about plan-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a research topic into sub-questions?▼

Provide the topic plus an optional depth (quick, standard, or deep) and audience. The skill generates 3–10 MECE sub-questions, each mapped to a coverage dimension with a rationale and expected source types, returned as one JSON object.

What is a MECE research plan?▼

A MECE plan uses coverage dimensions that are mutually exclusive and collectively exhaustive, so sub-questions do not overlap and together cover the topic. This skill picks 3–6 pillars from a catalog such as mechanisms, evidence, trade-offs, and counterpoints.

How does research depth affect the generated plan?▼

Depth sets a hard sub-question count: quick produces 3, standard produces 4–6, and deep produces 7–10. Deeper plans allow drilling into mechanisms, edge cases, and temporal shifts, while quick plans keep only the most load-bearing pillars.

Can this skill run the actual web searches for the research?▼

No. It only produces the plan; running searches is the job of the separate search-sources stage. The plan's out_of_scope list and notes_for_downstream guide that stage's queries.

What happens when the research topic is empty or unclear?▼

The skill emits a failure shape: all content fields empty, plan_skipped set to true, and the reason recorded in notes_for_downstream. Downstream stages treat this as a hard stop instead of guessing.