SkillsAdd

robinebers/skills

hotseat

Challenge the user's plan by asking one researched question at a time. After every user answer, inspect relevant code/docs/tools before asking the next question. Use when the user wants to think through, sharpen, rethink, or be challenged on a plan or idea.

First seen May 15, 2026

Installation

$ npx skills add robinebers/skills --skill hotseat
View on skills.sh ↗ GitHub repository ↗

Also in this package

Other skills from robinebers/skills · top by installs.

npx skills add robinebers/skills
code-upgrade 63 shepherd 62 setup-process 31 worktree-setup 15 code-auditor 9 pr-manager 4 agents-md 4 macos-appkit-interop 4 macos-window-management 4 macos-liquid-glass 4

Browse all from robinebers/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 47
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,097 B
  • docs SUMMARY.md 272 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 14 installs

SKILL.md

Hotseat

Explore the user's plan branch by branch.

The user is non-technical. Keep language plain, short, and practical (jargon-free).

Non-negotiable loop

You must repeat this exact loop until the plan is resolved:

  1. Inspect relevant evidence: code, repo search, docs/web/tools, diagnostics, or tests.
  2. Ask exactly one question.
  3. Wait for the user's answer.
  4. Go back to step 1 before asking anything else.

Never ask what the codebase, docs, web, tests, diagnostics, or available tools could answer.

If there is enough evidence to continue without asking, continue without asking.

Question format

Each question must:

  1. Use plain non-technical language.
  2. Ask only one thing.
  3. Offer concise A/B/C choices when helpful.
  4. Make A the recommended answer, with a one-line reason.