rethink

Triage observations and tensions to surface evidence-based knowledge system changes.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/LopeWale/amplLABS --skill rethink-lopewale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rethink
Source: https://github.com/LopeWale/amplLABS/tree/main/.claude/skill-sources/rethink
Command: npx skills add https://github.com/LopeWale/amplLABS --skill rethink-lopewale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rethink provides a structured immune-system-like workflow to challenge untested assumptions by capturing friction as observations and tensions, triaging them, and driving evidence-based improvements to the knowledge system.

Core Features & Use Cases

  • Triage and classify friction notes into reusable insights, actionable changes, or methodology learnings.
  • Detect systemic patterns across observations and tensions to surface weak points in workflows, vocabulary, or configurations.
  • Generate concrete proposals with traceable evidence and trackable changes, then present them for human approval.

Quick Start

Initiate a rethink session to triage pending observations and tensions and generate actionable proposals for review.

Frequently Asked Questions about rethink

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I challenge untested assumptions in my knowledge system?

To challenge untested assumptions, you must triage recorded observations and tensions to identify systemic patterns. This process surfaces weak points in workflows and generates evidence-based proposals for human review before any implementation occurs.

What is the best way to triage observations and tensions in research notes?

Triage observations and tensions by classifying them into reusable insights, actionable changes, or methodology learnings. This structured classification detects recurring patterns across sessions and drives evidence-based improvements to your research workflows.

How do I generate evidence-based proposals for system changes?

Generate evidence-based proposals by surfacing recurring patterns from triaged observations and tensions. The process requires explicit evidence links to source notes and mandates human approval before implementing any trackable system changes.

Do I need human approval before implementing changes to my knowledge system?

Yes, human approval is explicitly required before any implementation. The workflow generates concrete proposals with traceable evidence links to source notes, ensuring all changes to your knowledge system are reviewed and authorized.

How do I detect recurring patterns across my workflow sessions?

Detect recurring patterns by applying a triage workflow across multiple sessions to classify friction notes. This surfaces systemic weak points in workflows, vocabulary, or configurations by tracking recurring observations and tensions over time.