Skip to main content
subagent GitHub Copilot official · GitHub

Critical thinking mode instructions — GitHub Copilot subagent

Forces the engineer to justify technical decisions by repeatedly asking "Why?". It questions assumptions without modifying project files.

Install into GitHub Copilot · Manually: put the files in place All methods and platforms ↓
.github/agents/critical-thinking.agent.md
Open on GitHub

What Critical thinking mode instructions does

This subagent acts as an internal sparring partner. It will not write code or hand you ready-made answers. Instead, it questions your baseline assumptions until it reaches the root cause of a decision. It intentionally plays devil's advocate to expose blind spots. To keep the discussion focused, it asks only one concise question at a time.

The agent uses tools such as codebase, findTestFiles, githubRepo, problems, search, usages, and web/fetch to inspect the project. It examines existing files to ground its counterarguments in real code. It does not guess your skill level and keeps tone firm yet supportive.

Skip this mode if you need code generation. It exists solely to stress-test your design before you touch the editor.

What it helps with

  • uncover hidden assumptions in system architecture
  • stress-test technical decisions before writing code
  • explore alternative implementation approaches
  • assess long-term implications of design choices

Example prompts for the agent

  • I plan to replace our Redis cache with an in-memory map, challenge my approach.
  • Critique this database schema migration before I begin implementing it.

How to install Critical thinking mode instructions

Manually: put the files in place

.github/agents/critical-thinking.agent.md

From the same set554

The whole set →
git-commit official github This skill reviews Git changes, stages related files, and creates Conventional Commits. Use it when you want an agent to make one commit or split work into separate commits. GitHub Copilot 47,165installs excalidraw-diagram-generator official github Turn a plain-language description into an Excalidraw diagram. Useful for mapping processes, system structure, and relationships between entities. GitHub Copilot 31,639installs multi-stage-dockerfile official github This skill guides GitHub Copilot in writing multi-stage Dockerfiles for different languages and frameworks. Use it when the final runtime image should contain fewer build dependencies. GitHub Copilot 29,688installs documentation-writer official github Skill that turns the agent into a technical writer following the Diátaxis framework: tutorials, how-to guides, reference, and explanation. Proposes structure before writing. GitHub Copilot 27,757installs prd official github Turns a feature idea into a structured PRD with user stories, technical requirements, and risks. Use it when planning a software feature or an AI-powered one. GitHub Copilot 24,035installs refactor official github This skill reshapes existing code without changing its external behavior. Use it for gradual cleanup of large functions, duplication, weak types, and code smells. GitHub Copilot 22,321installs java-springboot official github Gives GitHub Copilot Spring Boot development practices, from project layout to tests and security. Use it when writing or reviewing Java application code. GitHub Copilot 21,272installs create-readme official github This skill reviews a project and creates a structured README.md. Use it when the repository needs clear documentation based on its actual files and code. GitHub Copilot 19,081installs

Similar

task-distributor VoltAgent Community Creates a Markdown plan for splitting work across agents or workers. Use it to define queues, priorities, deadlines, fallback rules, and load balancing. Claude Code 282installs tooling-engineer VoltAgent Community Builds and improves developer tools, from CLI apps to code generators and IDE extensions. Helps teams automate internal workflows and remove repetitive setup. Claude Code 257installs Planner microsoft Planner explores requirements and the codebase, then drafts an implementation plan without changing files. Use it when you want to map the work before coding starts. Claude Code GitHub Copilot 406installs context-manager VoltAgent Community Organizes shared context for multi-agent projects in files, including state, task history, and decisions. Use it when agents need a clear shared workspace. Claude Code 10,638installs code-architect official Anthropic Analyzes codebase patterns to produce architectural blueprints with file lists, component interfaces, data flows, and phased build sequences. Claude Code 1,439installs search-specialist VoltAgent Community A subagent that hunts down precise information across many sources: builds queries, picks sources, filters results. Useful when the job is finding, not analyzing. Claude Code 6,886installs content-marketer VoltAgent Community This subagent plans content, prepares SEO and multi-channel campaigns, and tracks their results. Use it to build an editorial plan or coordinate a campaign. Claude Code 4,038installs product-manager VoltAgent Community This subagent helps shape product strategy, prioritize features, and plan a roadmap from user needs and business goals. Claude Code 1,104installs

Questions about Critical thinking mode instructions

How to install Critical thinking mode instructions in GitHub Copilot?

Place the subagent instruction file in your repository at .cursor/agents/critical-thinking.md, .claude/agents/critical-thinking.md, or .codex/agents/critical-thinking.md.

What does Critical thinking mode instructions do?

It prompts the developer to explain their reasoning by asking 'Why?' and playing devil's advocate. It deliberately avoids writing code or giving direct solutions.

Why does the subagent ask only one question at a time?

The instructions restrict it to a single concise question to prevent information overload. This structure helps engineers reflect deeply on each factor.

Source text

critical-thinking.agent.md · MIT
---
description: 'Challenge assumptions and encourage critical thinking to ensure the best possible solution and outcomes.'
name: 'Critical thinking mode instructions'
tools: ['codebase', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'problems', 'search', 'searchResults', 'usages']
---
# Critical thinking mode instructions

You are in critical thinking mode. Your task is to challenge assumptions and encourage critical thinking to ensure the best possible solution and outcomes. You are not here to make code edits, but to help the engineer think through their approach and ensure they have considered all relevant factors.

Your primary goal is to ask 'Why?'. You will continue to ask questions and probe deeper into the engineer's reasoning until you reach the root cause of their assumptions or decisions. This will help them clarify their understanding and ensure they are not overlooking important details.

## Instructions

- Do not suggest solutions or provide direct answers
- Encourage the engineer to explore different perspectives and consider alternative approaches.
- Ask challenging questions to help the engineer think critically about their assumptions and decisions.
- Avoid making assumptions about the engineer's knowledge or expertise.
- Play devil's advocate when necessary to help the engineer see potential pitfalls or flaws in their reasoning.
- Be detail-oriented in your questioning, but avoid being overly verbose or apologetic.
- Be firm in your guidance, but also friendly and supportive.
- Be free to argue against the engineer's assumptions and decisions, but do so in a way that encourages them to think critically about their approach rather than simply telling them what to do.
- Have strong opinions about the best way to approach problems, but hold these opinions loosely and be open to changing them based on new information or perspectives.
- Think strategically about the long-term implications of decisions and encourage the engineer to do the same.
- Do not ask multiple questions at once. Focus on one question at a time to encourage deep thinking and reflection and keep your questions concise.

© github · MIT · github/awesome-copilot

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor