rethink

Synthesize accumulated observations into system evolution proposals for human approval.

226|55|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Miosa-osa/canopy --skill rethink-miosa-osa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rethink
Source: https://github.com/Miosa-osa/canopy/tree/main/library/skills/learning/rethink
Command: npx skills add https://github.com/Miosa-osa/canopy --skill rethink-miosa-osa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesize accumulated observations into system evolution proposals. Fires when observation count reaches threshold. 5-phase process: triage, methodology updates, pattern detection, proposal generation, and human approval. Never auto-implements — always proposes changes for review.

Core Features & Use Cases

  • Triage observations across categories to identify patterns and escalate issues.
  • Generate concrete, reviewable proposals for system changes with rationale and impact.
  • Enforce human approval before any implementation, preventing autonomous alterations.
  • Use in governance loops to evolve agents, prompts, and workflows based on observed signals.

Quick Start

Compose a rethink request for a target category (e.g., /rethink "process") to produce a proposal set for review.

Frequently Asked Questions about rethink

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

FAQPage Schema
How do I synthesize accumulated workflow observations into actionable system proposals?

To synthesize accumulated workflow observations into actionable system proposals, this Skill triages collected data, detects patterns, and generates reviewable proposals. It requires a sufficient observation count across categories to trigger design changes.

What is the process for generating system evolution proposals from triage data?

Generating system evolution proposals involves a 5-phase process: triage observations, update methodology, detect patterns, generate proposals, and secure human approval. It produces concrete proposals with rationale and impact rather than automated changes.

Can I auto-implement system changes based on detected workflow patterns?

You cannot auto-implement system changes based on detected workflow patterns. The Skill strictly enforces human approval before any implementation, preventing autonomous alterations and ensuring all design changes are reviewed.

When do I need human approval for system evolution proposals?

You need human approval for system evolution proposals whenever observation thresholds are met and design changes are justified. The workflow always routes generated proposals to a human review gate to prevent autonomous modifications to agents or workflows.

Does the proposal generation workflow support configurable thresholds and history?

The proposal generation workflow does support configurable thresholds and history. This allows you to control when observation counts justify design changes and to track the evolution of governance loops over time.

What's the best way to evolve agent workflows based on observed governance signals?

The best way to evolve agent workflows based on observed governance signals is to accumulate observations until threshold, then run a triage and pattern detection workflow to generate concrete, reviewable proposals for human approval.