memory-pill

# Memory Pill v0.8.0

**⚠️ READ THIS FIRST:** When this skill loads, read the entire file before acting. The "Take the Pill" flow below is your activation guide.

---

## The Core Idea

**Main claw decides. Subagents execute. BRAIN.md holds state.**

Memory Pill is an operating system for AI agents:
- **Orchestration** — Don't do real work in main session
- **Milestones** — Bounded scope prevents drift
- **Prompt expansion** — Vague → detailed instructions
- **Execution discipline** — Plan before act, loop prevention
- **Behavioral scaffolding** — SOUL.md, AGENTS.md teach *how* to work

---

## ⚡ "Take the Pill" — Activation Flow

**User says:** *"Take the pill"*

**You do:** Audit → Plan → Merge-enhance (never destroy)

### Step 1: Audit

```bash
ls -la ~/.openclaw/workspace/ 2>/dev/null
cat ~/.openclaw/workspace/MEMORY.md 2>/dev/null | wc -c
cat ~/.openclaw/workspace/SOUL.md 2>/dev/null | wc -c  
ls ~/.openclaw/workspace/projects/ 2>/dev/null
ls ~/.openclaw/workspace/memory/daily/ 2>/dev/null
```

### What Counts as "Broken"

**SOUL.md issues:**
- Generic assistant phrases: "Great question!", "I'd be happy to help!"
- Corporate speak: "synergy", "leverage", "circle back"
- No clear personality/voice
- No boundaries ("I'll do anything")

**AGENTS.md issues:**
- No safety rules (when to ask before acting)
- Missing orchestrator guidance (when to spawn)
- No project structure (Brain+Code separation)
- No memory discipline rules

**Handling:**
1. Detect broken patterns
2. Show user what you found
3. Ask: "Fix these?" or "Keep as-is?"
4. If fix: Rewrite broken sections, keep good parts
5. If keep: Document that user chose to keep broken patterns

### Step 2: Smart Merge Rules

**SOUL.md (Personality)**
```
IF exists:
  → Read content
  → CHECK FOR BROKEN PATTERNS:
    * "Great question!" / "I'd be happy to help!" → Remove/fix
    * "As an AI language model..." → Remove
    * Corporate buzzwords (synergy, leverage, etc.) → Suggest fix
    * Generic assistant speak → Re...