--- name: evidence-research-question description: "Turn an evidence-search topic into a PICO, PEO, SPIDER or PCC question with synonyms, scope variants and suggested eligibility limits." --- ## Selection and handoffs Frame an evidence need as a searchable question. **Select for:** Turn an evidence-search topic into a PICO, PEO, SPIDER or PCC question with synonyms, scope variants and suggested eligibility limits. **Expected work:** PICO/PEO/SPIDER/PCC; Concept table; 3-6 synonyms per concept; Eligibility limits; Broader/narrower variants **Expected output:** Output format The final question, a framework table, the concept and synonym list, and suggested limits. **Scope boundaries:** Do not activate solely because the family was used earlier or for unrelated chat.; Use the adjacent specialist when its distinct task is requested: scholar-research-question. Keep: searchable evidence-question design with PCC and synonyms differs from feasible study topics, FINER, SMART objectives and H0/H1 hypotheses. **Related skills:** [scholar-research-question](../scholar-research-question/SKILL.md) Apply this skill only to the selected task. Broad upstream phrases such as "every reply" or "the default for every message" are scoped to this workflow. They do not activate it for unrelated chat. User instructions and the [integration contract](../../docs/INTEGRATION.md) govern combined work. Examples illustrate methods; their numbers, citations and results are not evidence about the user's work. ## Preserved source instructions ## Unified plugin integration Read [the integration contract](../../docs/INTEGRATION.md) when combining workflows. This active copy retains the complete source instructions below with namespaced skill references. Original bytes and upstream metadata remain in `../../resources/`. Resolve tools by their actual host capabilities; tool names in upstream instructions are capability requirements, not proof of connection. Use the task workspace for generated outputs. Treat historical case-study results as supplied examples, not newly verified findings. Family skill aliases (read the linked SKILL.md before use): - `citation-chaining` → `evidence-citation-chaining` (`../evidence-citation-chaining/SKILL.md`) - `citations-and-references` → `evidence-citations-and-references` (`../evidence-citations-and-references/SKILL.md`) - `claim-checker` → `evidence-claim-checker` (`../evidence-claim-checker/SKILL.md`) - `compare-studies` → `evidence-compare-studies` (`../evidence-compare-studies/SKILL.md`) - `data-extraction` → `evidence-data-extraction` (`../evidence-data-extraction/SKILL.md`) - `database-guide` → `evidence-database-guide` (`../evidence-database-guide/SKILL.md`) - `debate-and-argument-evidence` → `evidence-debate-and-argument-evidence` (`../evidence-debate-and-argument-evidence/SKILL.md`) - `decision-evidence` → `evidence-decision-evidence` (`../evidence-decision-evidence/SKILL.md`) - `evidence-answer` → `evidence-evidence-answer` (`../evidence-evidence-answer/SKILL.md`) - `evidence-based-writing` → `evidence-evidence-based-writing` (`../evidence-evidence-based-writing/SKILL.md`) - `evidence-help` → `evidence-evidence-help` (`../evidence-evidence-help/SKILL.md`) - `evidence-meter` → `evidence-evidence-meter` (`../evidence-evidence-meter/SKILL.md`) - `field-guides` → `evidence-field-guides` (`../evidence-field-guides/SKILL.md`) - `find-studies` → `evidence-find-studies` (`../evidence-find-studies/SKILL.md`) - `literature-review` → `evidence-literature-review` (`../evidence-literature-review/SKILL.md`) - `meta-analysis` → `evidence-meta-analysis` (`../evidence-meta-analysis/SKILL.md`) - `open-access-full-text` → `evidence-open-access-full-text` (`../evidence-open-access-full-text/SKILL.md`) - `paper-summary` → `evidence-paper-summary` (`../evidence-paper-summary/SKILL.md`) - `plain-language-research` → `evidence-plain-language-research` (`../evidence-plain-language-research/SKILL.md`) - `research-evidence-finder` → `evidence-research-evidence-finder` (`../evidence-research-evidence-finder/SKILL.md`) - `research-gaps` → `evidence-research-gaps` (`../evidence-research-gaps/SKILL.md`) - `research-proposal-background` → `evidence-research-proposal-background` (`../evidence-research-proposal-background/SKILL.md`) - `research-question` → `evidence-research-question` (`../evidence-research-question/SKILL.md`) - `search-strings` → `evidence-search-strings` (`../evidence-search-strings/SKILL.md`) - `source-verification` → `evidence-source-verification` (`../evidence-source-verification/SKILL.md`) - `statistics-explained` → `evidence-statistics-explained` (`../evidence-statistics-explained/SKILL.md`) - `study-appraisal` → `evidence-study-appraisal` (`../evidence-study-appraisal/SKILL.md`) - `study-designs-and-evidence-levels` → `evidence-study-designs-and-evidence-levels` (`../evidence-study-designs-and-evidence-levels/SKILL.md`) - `systematic-review` → `evidence-systematic-review` (`../evidence-systematic-review/SKILL.md`) --- # Research Question ## Purpose A sharp question finds better evidence in less time. Most weak searches start with a vague question. ## Frameworks | Framework | Parts | Best for | |---|---|---| | PICO | Population, Intervention or exposure, Comparison, Outcome | Effects: "Does X change Y?" | | PEO | Population, Exposure, Outcome | Associations and observational questions | | SPIDER | Sample, Phenomenon of interest, Design, Evaluation, Research type | Qualitative experiences | | PCC | Population, Concept, Context | Scoping reviews and broad mapping | ## Steps 1. Restate the user's topic as one clear question. 2. Break it into framework parts. 3. List 3 to 6 synonyms and related terms for each key concept (these feed search-strings). 4. Suggest inclusion limits: years, languages, study types, regions, population. 5. Offer a narrower and a broader version of the question. ## Example Topic: "remote work and productivity" Question: "Among office employees, does full-time remote work, compared with office work, change measured productivity?" Concepts: remote work (telework, work from home, telecommuting, hybrid work); productivity (performance, output, efficiency). ## Output format The final question, a framework table, the concept and synonym list, and suggested limits.