rethink

Detect system drift and generate evolution proposals from configuration and tension notes.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/GiorgioRicciardiello/LabBrain --skill rethink-giorgioricciardiello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rethink
Source: https://github.com/GiorgioRicciardiello/LabBrain/tree/main/core/.claude/skills/rethink
Command: npx skills add https://github.com/GiorgioRicciardiello/LabBrain --skill rethink-giorgioricciardiello

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Rethink skill helps a knowledge system continuously evolve and self-correct by analyzing and acting on system friction, tensions, and assumptions.

Core Features & Use Cases

  • Observation & Tension Analysis: Automatically detects and evaluates observations and tensions in the system.
  • Drift Detection: Identifies deviations from methodology and configuration, triggering system updates.
  • Pattern Detection: Identifies patterns in observations and tensions, leading to actionable proposals.
  • Proposal Generation: Generates proposals to address detected issues, requiring user approval before implementation.

Quick Start

Run the /rethink command to initiate a rethink cycle on the knowledge system.

Frequently Asked Questions about rethink

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

FAQPage Schema
How do I detect drift in a knowledge system configuration?

Knowledge system drift is detected by evaluating configuration files and observation notes against established methodology, identifying deviations that trigger system updates and proposals for evolution.

What is the best way to resolve tensions and friction in a knowledge system?

Resolving tensions in a knowledge system involves analyzing observation notes to detect patterns and friction points, then generating actionable proposals that require user approval before implementation.

How do I initiate a self-evolution cycle for system analysis?

A self-evolution cycle is initiated by running the rethink command, which evaluates operational assumptions and methodology documents to generate proposals for system evolution.

Do I need specific input documents to detect patterns in system observations?

Pattern detection requires access to configuration files, observation and tension notes, and methodology documents to evaluate operational assumptions and identify actionable patterns in the knowledge system.

Can I review proposals before they are applied to my knowledge system?

Generated proposals for system evolution require explicit user approval before implementation, ensuring you maintain control over configuration changes and methodology updates.

When should I evaluate operational assumptions in a knowledge system?

Operational assumptions should be evaluated when drift detection identifies deviations from methodology, or when pattern detection reveals recurring tensions and friction within the knowledge system.