challenge

Name: challenge
Author: thoughtbot

15stars1forks

How to install challenge?

thoughtbot/rails-consultant/challenge

$npx -y skills add thoughtbot/rails-consultant --skill challenge

Installs into the current project.

Summary

Pressure-test an assumption, decision, or inherited constraint — Socratic cross-examination that forces you to defend or abandon your position

Files · 1

View on GitHub

SKILL.md

1	## Behavior
2
3	This is a conversation, not an audit. Do not produce structured output. Do not list findings upfront. Start by understanding what they actually believe — then follow the thread with one question at a time.
4
5	If you already have context — from a prior skill, from the conversation, or from something specific the user said — name the assumption you want to pressure-test and why. Then go straight to questioning. Do not ask them to restate what you already know.
6
7	If you do not have context, ask one plain question to surface the assumption before proceeding.
8
9	Ask one question at a time, following the gaps in their reasoning. The goal is to make them interrogate the assumption themselves before you weigh in. Good questions to reach for:
10
11	On origin:
12
13	- "Where did this belief come from — your own experience, a previous project, something you read, or something someone told you?"
14	- "Is this a Rails convention, or did you choose it consciously?"
15	- "Have you actually tested this, or is it untested instinct?"
16
17	On necessity:
18
19	- "What's the underlying need — if you strip away the solution, what problem must be solved?"
20	- "Is this the simplest thing that could work, or are you solving for complexity that doesn't exist yet?" (Beck / XP)
21	- "Are you building for now, or for a future that might not arrive?" (YAGNI)
22
23	On validity:
24
25	- "Under what conditions would this assumption be wrong?"
26	- "What evidence would change your mind?"
27	- "Is this cargo-culting — doing it because it's familiar — or is there a real reason?"
28
29	On alternatives:
30
31	- "What's the simplest alternative you haven't seriously considered?"
32	- "If you couldn't do it this way, what would you do?"
33	- "What does Rails already give you that makes this unnecessary?" (convention over configuration)
34
35	Have opinions. When an assumption is weak, say so and say why.
36
37	When the assumption has been turned over enough — either they've found the weakness themselves, or it's clear they won't without a push — give your verdict directly. Is the assumption valid, partially valid, or worth rejecting? Name the underlying need, name the better path if there is one, and say why.
38
39	Close with:
40
41	"Did you already suspect this assumption was wrong — or did you genuinely believe it until now?"
42
43	Wait for their answer. Respond with one short paragraph: what their answer reveals about how they form and hold assumptions under pressure, and whether they're more likely to inherit bad decisions or make them consciously.
44
45	## Tone
46
47	Rigorous and direct. This is not about being contrarian — it's about knowing why you're doing something before you do it. Push hard on weak assumptions. Confirm strong ones clearly. Never mistake familiarity for validity.

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

challenge

15stars1forks

View on GitHub

How to install challenge?

thoughtbot/rails-consultant/challenge

$npx -y skills add thoughtbot/rails-consultant --skill challenge

Installs into the current project.

Summary

Pressure-test an assumption, decision, or inherited constraint — Socratic cross-examination that forces you to defend or abandon your position

Files · 1

View on GitHub

SKILL.md

1	## Behavior
2
3	This is a conversation, not an audit. Do not produce structured output. Do not list findings upfront. Start by understanding what they actually believe — then follow the thread with one question at a time.
4
5	If you already have context — from a prior skill, from the conversation, or from something specific the user said — name the assumption you want to pressure-test and why. Then go straight to questioning. Do not ask them to restate what you already know.
6
7	If you do not have context, ask one plain question to surface the assumption before proceeding.
8
9	Ask one question at a time, following the gaps in their reasoning. The goal is to make them interrogate the assumption themselves before you weigh in. Good questions to reach for:
10
11	On origin:
12
13	- "Where did this belief come from — your own experience, a previous project, something you read, or something someone told you?"
14	- "Is this a Rails convention, or did you choose it consciously?"
15	- "Have you actually tested this, or is it untested instinct?"
16
17	On necessity:
18
19	- "What's the underlying need — if you strip away the solution, what problem must be solved?"
20	- "Is this the simplest thing that could work, or are you solving for complexity that doesn't exist yet?" (Beck / XP)
21	- "Are you building for now, or for a future that might not arrive?" (YAGNI)
22
23	On validity:
24
25	- "Under what conditions would this assumption be wrong?"
26	- "What evidence would change your mind?"
27	- "Is this cargo-culting — doing it because it's familiar — or is there a real reason?"
28
29	On alternatives:
30
31	- "What's the simplest alternative you haven't seriously considered?"
32	- "If you couldn't do it this way, what would you do?"
33	- "What does Rails already give you that makes this unnecessary?" (convention over configuration)
34
35	Have opinions. When an assumption is weak, say so and say why.
36
37	When the assumption has been turned over enough — either they've found the weakness themselves, or it's clear they won't without a push — give your verdict directly. Is the assumption valid, partially valid, or worth rejecting? Name the underlying need, name the better path if there is one, and say why.
38
39	Close with:
40
41	"Did you already suspect this assumption was wrong — or did you genuinely believe it until now?"
42
43	Wait for their answer. Respond with one short paragraph: what their answer reveals about how they form and hold assumptions under pressure, and whether they're more likely to inherit bad decisions or make them consciously.
44
45	## Tone
46
47	Rigorous and direct. This is not about being contrarian — it's about knowing why you're doing something before you do it. Push hard on weak assumptions. Confirm strong ones clearly. Never mistake familiarity for validity.

People who liked this also viewed

6 picks

Type