octocode-awareness

Use when you need agent memory, file locks, or verify-before-conclude across runs and concurrent agents on a coding task — before/after big changes, edits, design, or handoffs in a shared or dirty local repo. Self-awareness — recall shared memory + work-handoff refinements (open/ongoing/done) before acting (recall is salience-decayed), record reusable lessons after. Self-harness — verify before you conclude (run your test-plan and record it; never claim success on an unverified intent), mine recurring failures, and propose refinements to code or the harness when asked or when you sense one is needed. Files-awareness — you MUST take a pre-flight file lock BEFORE creating, editing, or deleting any file, then release; check status and timestamps first. Triggers on agent memory, refinements, file locks, shared-workspace edits, dirty working tree, handoffs, repeated failures, unverified conclusions, or harness/code refinement.