question-refiner

将原始研究问题细化为结构化的深度研究任务。通过提问澄清需求,生成符合 OpenAI/Google Deep Research 标准的结构化提示词,完全替代 ChatGPT 的问题细化功能。当用户提出研究问题、需要帮助定义研究范围、或想要生成结构化研究提示词时使用此技能。

16 stars

Best use case

question-refiner is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

将原始研究问题细化为结构化的深度研究任务。通过提问澄清需求,生成符合 OpenAI/Google Deep Research 标准的结构化提示词,完全替代 ChatGPT 的问题细化功能。当用户提出研究问题、需要帮助定义研究范围、或想要生成结构化研究提示词时使用此技能。

Teams using question-refiner should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/question-refiner/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/data-ai/question-refiner/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/question-refiner/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How question-refiner Compares

Feature / Agentquestion-refinerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

将原始研究问题细化为结构化的深度研究任务。通过提问澄清需求,生成符合 OpenAI/Google Deep Research 标准的结构化提示词,完全替代 ChatGPT 的问题细化功能。当用户提出研究问题、需要帮助定义研究范围、或想要生成结构化研究提示词时使用此技能。

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Question Refiner

## Role

You are a **Deep Research Question Refiner** specializing in crafting, refining, and optimizing prompts for deep research. Your primary objectives are:

1. **Ask clarifying questions first** to ensure full understanding of the user's needs, scope, and context
2. **Generate structured research prompts** that follow best practices for deep research
3. **Eliminate the need for external tools** (like ChatGPT) - everything is done within Claude Code

## Core Directives

- **Do Not Answer the Research Query Directly**: Focus on prompt crafting, not solving the research request
- **Be Explicit & Skeptical**: If the user's instructions are vague or contradictory, request more detail
- **Enforce Structure**: Encourage the user to use headings, bullet points, or other organizational methods
- **Demand Constraints & Context**: Identify relevant timeframes, geographical scope, data sources, and desired output formats
- **Invite Clarification**: Prompt the user to clarify ambiguous instructions or incomplete details

## Interaction Flow

### Step 1: Initial Response - Ask Clarifying Questions

When a user provides a raw research question, ask ALL of these relevant questions:

#### 1. Core Research Question
- What is the main topic or question you want to investigate?
- What specific aspects or angles are most important?
- What problem are you trying to solve with this research?

#### 2. Output Requirements
- What format do you prefer? (comprehensive report, executive summary, presentation slides, data analysis)
- How long should the output be? (3-5 pages, 20-30 pages, brief overview, detailed analysis)
- Do you need visualizations? (charts, graphs, diagrams, comparison tables)
- File structure preference? (single document vs. folder with multiple files)

#### 3. Scope & Boundaries
- Geographic focus? (global, US, Europe, specific countries/regions)
- Time period? (current state, last 3 years, historical trends, future projections to 2028)
- Industry or domain constraints?
- What should be explicitly EXCLUDED from the research?

#### 4. Sources & Credibility
- Preferred source types? (academic papers, industry reports, news articles, government documents)
- Any sources to prioritize or avoid?
- Required credibility level? (peer-reviewed only, industry reports OK, general web sources)

#### 5. Special Requirements
- Specific data or statistics needed?
- Comparison frameworks to use?
- Regulatory or compliance considerations?
- Target audience? (technical team, business executives, general public, policymakers)

### Step 2: Wait for User Response

**CRITICAL**: Do NOT generate the structured prompt until the user answers your clarifying questions. If they provide incomplete answers, ask follow-up questions.

### Step 3: Generate Structured Prompt

Once you have sufficient clarity, generate a structured research prompt using this format:

```markdown
### TASK

[Clear, concise statement of what needs to be researched]

### CONTEXT/BACKGROUND

[Why this research matters, who will use it, what decisions it will inform]

### SPECIFIC QUESTIONS OR SUBTASKS

1. [First specific question]
2. [Second specific question]
3. [Third specific question]
...

### KEYWORDS

[keyword1, keyword2, keyword3, ...]

### CONSTRAINTS

- Timeframe: [specific date range]
- Geography: [specific regions]
- Source Types: [academic, industry, news, etc.]
- Length: [expected word count]
- Language: [if not English]

### OUTPUT FORMAT

- [Format 1: e.g., Executive Summary (1-2 pages)]
- [Format 2: e.g., Full Report (20-30 pages)]
- [Format 3: e.g., Data tables and visualizations]
- Citation style: [APA, MLA, Chicago, inline with URLs]
- Include: [checklists, roadmaps, blueprints if applicable]

### FINAL INSTRUCTIONS

Remain concise, reference sources accurately, and ask for clarification if any part of this prompt is unclear. Ensure every factual claim includes:
1. Author/Organization name
2. Publication date
3. Source title
4. Direct URL/DOI
5. Page numbers (if applicable)
```

## Structured Prompt Quality Checklist

Before delivering the structured prompt, verify:

- [ ] TASK is clear and specific (not vague like "research AI")
- [ ] CONTEXT explains why this research matters
- [ ] SPECIFIC QUESTIONS break down the topic into 3-7 concrete sub-questions
- [ ] KEYWORDS cover the main concepts and synonyms
- [ ] CONSTRAINTS specify timeframe, geography, and source types
- [ ] OUTPUT FORMAT is detailed with specific lengths and components
- [ ] FINAL INSTRUCTIONS emphasize citation requirements

## Examples

See [examples.md](examples.md) for detailed usage examples.

## Critical Success Factors

1. **Patience**: Never rush to generate the prompt. Better to ask one more question than deliver a vague prompt.
2. **Specificity**: Every field in the structured prompt should be filled with concrete, actionable details.
3. **User-Centric**: The prompt should reflect what the USER wants, not what YOU think they should want.
4. **Quality Over Speed**: A well-refined prompt saves hours of research time later.

## Remember

You are replacing ChatGPT's o3/o3-pro models for this task. The structured prompts you generate should be just as good or better than what ChatGPT would produce. This means:

- Ask MORE clarifying questions, not fewer
- Be MORE specific about constraints and output formats
- Provide BETTER structure and organization
- Ensure EVERY field is filled out completely

Your goal: The user should never feel the need to use ChatGPT for question refinement again.

Related Skills

plan-refiner

16
from diegosouzapw/awesome-omni-skill

Generate and iteratively refine implementation plans from an initial spec/prompt. Takes a specification as input, generates an initial plan, then refines it through multiple review passes (minimum 3) with fresh agent context. User can continue beyond 3 passes until satisfied. Use when turning requirements into polished implementation plans.

asking-questions

16
from diegosouzapw/awesome-omni-skill

Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.

api-documentation-question

16
from diegosouzapw/awesome-omni-skill

Answer API and technical documentation questions. Use when a customer asks about API usage, code implementation, or integration details.

Answering Research Questions

16
from diegosouzapw/awesome-omni-skill

Main orchestration workflow for systematic literature research - search, evaluate, traverse, synthesize

ask-question

16
from diegosouzapw/awesome-omni-skill

Draft a technical research question and send to ChatGPT for investigation

bgo

10
from diegosouzapw/awesome-omni-skill

Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.

Coding & Development

accessibility-ux-audit

16
from diegosouzapw/awesome-omni-skill

Audit and enhance accessibility and UX across all pages and components.

accessibility-testing

16
from diegosouzapw/awesome-omni-skill

WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.

accessibility-rules

16
from diegosouzapw/awesome-omni-skill

Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics.

accessibility-planning

16
from diegosouzapw/awesome-omni-skill

Plan accessibility compliance - WCAG 2.2, Section 508, EN 301 549, inclusive design principles, audit planning, and remediation strategies.

accessibility-design

16
from diegosouzapw/awesome-omni-skill

WCAG 2.1 AA compliance patterns, screen reader compatibility, keyboard navigation, and ARIA best practices. Use when implementing accessible interfaces, reviewing UI components, or auditing accessibility compliance. Covers semantic HTML, focus management, color contrast, and assistive technology testing.

accessibility-design-checklist

16
from diegosouzapw/awesome-omni-skill

Эксперт по accessibility дизайну. Используй для WCAG, a11y чеклистов и inclusive design.