VI (6)

argus-retrospective-capture

argus

Use to capture reusable lessons from Codex work, identify repeated friction, propose skill or reference improvements, and prevent uncontrolled memory or context bloat.

Argus Retrospective Capture

IPurpose

Turn repeated workflow friction into controlled improvement proposals.

IILearning Rule

Argus does not silently mutate itself. Capture lessons as proposed updates, then apply them only when the user approves or explicitly asks for implementation.

IIIWorkflow

  1. Separate one-off events from reusable lessons.
  2. Identify whether the lesson belongs in a skill, script, reference, hook, or repo instruction.
  3. Prefer the smallest durable location.
  4. Keep SKILL.md concise; move details into references.
  5. Validate after any approved update.

IVOutput

Return:

  • observed pattern
  • proposed durable home
  • why it belongs there
  • context-bloat risk
  • recommended next change
← back to the stoa