rethink

Solid

EXPERIMENTAL. Use when options, a recommendation, or an already-chosen approach are on the table and the reasoning under them has not been independently checked — especially when the case rests on cited documentation, remembered behavior, or premises nobody verified. Not for generating alternatives, and not for critiquing a spec, which is /pushback.

Code & Development 114 stars 10 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
69
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

**On invocation:** announce "Running paad:rethink v1.31.0" before anything else. # Rethink **Experimental.** Arguments, verdicts, and output shape may change — or this skill may be withdrawn — in any release, including a patch release. The semver promise the settled skills carry does not apply here. If you build a workflow on it, pin your plugin version and [file what breaks](https://github.com/Ovid/paad/issues). Checks whether the reasoning under a set of options actually holds. Someone — you, the user, or another skill — laid out choices and picked one. `rethink` goes and verifies the premises that choice rests on, against primary sources, and reports what it found. **A recommendation can be correct and still be unsound.** The two most common results are not "right" and "wrong" — they are *right, and checked* versus *right, and merely lucky*. A conclusion that happens to hold, arrived at by trusting a source nobody tested, will hold until the day it doesn't, and nobody will be watching. Saying so is the point of this skill. **`rethink` does not owe you alternatives.** It is not `pushback`. It has no obligation to produce an option list, and manufacturing one is the failure mode it exists to avoid. A grounded defect can motivate exactly one alternative. Nothing else can. **`rethink` writes nothing.** No report, no edits, no files in the repository, and no deliverable of any kind — the conversation is the whole output. A scratch dump outside the repo, to hold a `strings...

Details

Author
Ovid
Repository
Ovid/paad
Created
6 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Featured

think

Use when you have a rough idea and want it sharpened before any code is written. Refines the idea through questions, one at a time. Explores 2-3 approaches with trade-offs. Walks the design with you, section by section. Saves a brief your next steps read. Still challenges scope and finds the smallest starting point. Supports --autopilot to run the full sprint automatically after approval. Use --retro after a sprint to reflect on what shipped. Triggers on /think, /office-hours, /ceo-review.

206 Updated yesterday
garagon
AI & Automation Listed

recursive-thinking

Adversarial review workflow for pressure-testing an existing candidate plan, diagnosis, design, argument, proposal, or recommendation. Use when the user asks to challenge its assumptions, run a premortem, play devil's advocate, red-team a non-security decision, or identify what would change the conclusion. Do not use for open-ended exploration (use thinking) or exploit-focused security review (use security as primary).

4 Updated 5 days ago
n-n-code
AI & Automation Solid

sequential-thinking

Structured reasoning harness for problems where shallow thinking fails or hallucination is costly. Use whenever a question requires multi-step reasoning, involves competing hypotheses, has multiple interacting components, or carries irreversible consequences. Activate for debugging with unclear root causes, intermittent or multi-component issues, incident post-mortems, choosing between multiple valid approaches, architecture or design tradeoffs, causal chain analysis, high-stakes decisions, and any task where the first plausible answer is suspiciously easy. Provides reasoning modes (abductive, counterfactual, first-principles, inversion, and more), grounding techniques against confabulation, adversarial self-checks, root-cause playbooks, and automatic multi-approach synthesis (independent angles run in parallel and compared) — all through the `mcp__sequential-thinking__sequentialthinking` tool. Skip for trivial lookups, obvious fixes, and single-step questions.

13 Updated 5 days ago
app-builders-club