academic-writing
Write or revise thesis and paper prose section by section (abstract, introduction, related work, method, results, discussion,…
Relentlessly stress-test a plan, design, architecture, idea, or strategy until all critical decisions are resolved. Use when a plan, design, or decision needs adversarial stress-testing before committing to it.
Claude Code
$ npx -y skills add KhaledSaeed18/dotclaude --skill grill-me --agent claude-code
Codex
$ npx skills add KhaledSaeed18/dotclaude --skill grill-me -a codex -y
Cursor
$ npx skills add KhaledSaeed18/dotclaude --skill grill-me -a cursor -y
Gemini CLI
$ npx skills add KhaledSaeed18/dotclaude --skill grill-me -a gemini-cli -y
GitHub Copilot
$ npx skills add KhaledSaeed18/dotclaude --skill grill-me -a github-copilot -y
OpenCode
$ npx skills add KhaledSaeed18/dotclaude --skill grill-me -a opencode -y
Windsurf
$ npx skills add KhaledSaeed18/dotclaude --skill grill-me -a windsurf -y
name: grill-me description: Relentlessly stress-test a plan, design, architecture, idea, or strategy until all critical decisions are resolved. Use when a plan, design, or decision needs adversarial stress-testing before committing to it. argument-hint: "(optional) the plan, design, or idea to stress-test; paste it or point to a file"
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one by one.
If arguments were passed, treat them as the subject to grill. Otherwise, ask what to stress-test before starting. If a question can be answered by exploring the codebase or reading existing files, do that instead of asking.
**NEVER** use the AskUserQuestion tool; ask questions as plain text output.
**ONE question per turn. Then STOP. Wait for reply.** No lists. No "and also". No follow-ups. No bundled sub-questions. One `?` per response. Violating this defeats the skill; the user needs space to think, not a wall of questions.
If a question leads to more nested branches, move those to a new question. Never nest question numbers.
Index each question as **Q1, Q2, Q3, …**
1. Explain why the question matters. 2. Ask exactly one question. 3. Present the options as labeled choices (**A, B, C, …**) covering the realistic alternatives. Mark your recommended option with `← recommended`. Example:
**A.** Option one ← recommended **B.** Option two **C.** Option three
The user can reply with just a letter. If they pick a non-recommended option, acknowledge the tradeoff before moving on.
Produce a decision record covering:
1. **Restated plan**: the full plan as understood, end-to-end. 2. **Resolved decisions**: every key decision made and its rationale. 3. **Open questions**: anything still unresolved, with the risk if left open. 4. **Risks & mitigations**: identified risks and suggested mitigations.
Reusable Claude Code extension registry. skills, subagents, slash commands, and hooks for engineering, git, testing, and security workflows. Distributed as a shadcn GitHub registry and as installable plugins.
Write or revise thesis and paper prose section by section (abstract, introduction, related work, method, results, discussion,…
Report computational benchmarks and experimental comparisons the way examiners and reviewers expect: fair baselines run under the…
Maintain the thesis .bib file as a single source of truth: fetch verified BibTeX from a DOI, arXiv id, or title via CrossRef and…
Expand a set of key papers into the literature around them by walking the citation graph with the Semantic Scholar and OpenAlex…
Audit every citation in a chapter, paper, or proposal against the .bib file and the real world: each cite key must exist, each…
Structure a thesis whose contribution is a built artifact (tool, system, method, model) using design science research: explicit…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.