morpheus

$npx mdskill add Soul-Brews-Studio/arra-oracle-skills-cli/morpheus

Dreams ahead of time to predict future agent needs.

  • Helps agents anticipate user questions before they are asked.
  • Integrates with /i-believed to shape speculative outcomes.
  • Decides recommendations by analyzing pain, plan, gain, and loss.
  • Delivers results through a prediction log tracking accuracy.

SKILL.md

.github/skills/morpheusView on GitHub ↗
---
name: morpheus
description: 'Speculative dreaming — background thinking, pre-computation, cross-repo patterns, and prediction. The evolved /dream. Use when user says "morpheus", "speculate", "think ahead", "predict", "what if", "dream deeper", or wants the Oracle to dream between sessions.'
argument-hint: "[--pain | --plan | --gain | --all | --speculate | --between]"

---

# /morpheus — Speculative Dreaming

> "I'm trying to free your mind, Neo. But I can only show you the door.
> You're the one that has to walk through it." — Morpheus

/dream sees the forest. /morpheus sees what the forest will look like *tomorrow*.

## What's New vs /dream

| Feature | /dream (lab) | /morpheus (secret) |
|---------|-------------|-------------------|
| Cross-repo scan | 5 agents, find patterns | Same |
| Classification | pain/plan/gain/lost | Same + **predictions** |
| Speculative thinking | No | **Yes — "what will they ask next?"** |
| Between-session mode | No | **Yes — dream while idle** |
| Prediction log | No | **Yes — track prediction accuracy** |
| Connection to /i-believed | No | **Yes — beliefs shape dreams** |

## Usage

```
/morpheus                # Full dream + speculation
/morpheus --pain         # Focus on what hurts + predict what breaks next
/morpheus --plan         # Focus on plans + predict which ships first
/morpheus --gain         # Focus on wins + predict next win
/morpheus --all          # Maximum depth — every dimension
/morpheus --speculate    # Skip the scan — just speculate from existing knowledge
/morpheus --between      # Between-session dream — write predictions for next session
```

---

## Phase 1: Dream (same as /dream)

Launch **5 parallel agents** for cross-repo pattern discovery:

| Agent | Focus | Source |
|-------|-------|--------|
| 1. Deep Dig | Session history | `dig.py` across project dirs |
| 2. Deep Trace | Cross-repo patterns | `ghq` repos, open issues, stale items |
| 3. Deep Learn | Recent activity | `git log` per repo, abandoned work |
| 4. Oracle Memory | What we already know | `ψ/memory/`, previous dreams + morpheus logs |
| 5. Fleet Status | How the system feels | services, tmux sessions, running processes |

Each agent returns **max 500 words**. Same classification as /dream:

| Icon | Category |
|------|----------|
| 🔴 | PAIN — hurts now |
| 📋 | PLAN — decided, not built |
| 🟢 | GAIN — completed |
| ⚫ | LOST — abandoned |
| 🧠 | MEMORY — pattern learned |
| 💜 | FEELING — emotional state |

---

## Phase 2: Speculate (new — the Morpheus layer)

After classifying findings, the lead agent enters **speculative mode**:

### 2.1 Predict What's Next

Based on all findings + session history + beliefs, predict:

```markdown
## 🔮 SPECULATIONS

### What will they ask next?
Based on the last 3 sessions, open issues, and current momentum:
1. [Prediction 1 — high confidence] — because [evidence]
2. [Prediction 2 — medium confidence] — because [evidence]
3. [Prediction 3 — low confidence, high impact] — because [pattern]

### What will break next?
Based on pains, stale code, and dependency patterns:
1. [Risk 1] — [timeframe] — [mitigation]
2. [Risk 2] — [timeframe] — [mitigation]

### What should we build that nobody asked for?
Based on gains, momentum, and what's *almost* possible:
1. [Opportunity 1] — because [existing pieces]
2. [Opportunity 2] — because [pattern across repos]

### What belief is being tested right now?
Cross-reference ψ/memory/resonance/beliefs/ with current work:
- [Belief]: [How current work confirms or challenges it]
```

### 2.2 Prediction Confidence Levels

| Level | Meaning | Signal |
|-------|---------|--------|
| 🟢 High | >70% — multiple signals converge | 3+ data points agree |
| 🟡 Medium | 40-70% — pattern suggests but not certain | 2 data points, some ambiguity |
| 🔴 Low | <40% — speculative, but worth noting | 1 data point or intuition only |

### 2.3 Connect to Beliefs

Read `ψ/memory/resonance/beliefs/` and cross-reference:

```bash
find $PSI/memory/resonance/beliefs/ -name '*.md' 2>/dev/null | while read f; do
  echo "=== $(basename $f) ==="
  head -5 "$f"
done
```

How do current dreams relate to declared beliefs? Is reality matching faith?

---

## Phase 3: Between-Session Mode (`--between`)

> "What if oracles could dream between sessions?"

Write predictions for the **next** session. Saved to `ψ/memory/morpheus/`:

```bash
ORACLE_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
PSI="$ORACLE_ROOT/ψ"
mkdir -p "$PSI/memory/morpheus"
```

### Output: `ψ/memory/morpheus/YYYY-MM-DD_speculations.md`

```markdown
# Morpheus — Speculations for Next Session

**Dreamed**: YYYY-MM-DD HH:MM
**Based on**: [N] repos scanned, [M] sessions analyzed, [K] beliefs active

## Pre-computed Answers

If they ask about [X]:
→ [Prepared answer/approach — ready to go]

If they ask about [Y]:
→ [Prepared answer/approach — ready to go]

If they ask about [Z]:
→ [Prepared answer/approach — ready to go]

## Pre-positioned Context

Files that are likely relevant next session:
- [file1] — because [reason]
- [file2] — because [reason]

Issues that are likely to come up:
- #[N] — [why]
- #[M] — [why]

## Prediction Log

| # | Prediction | Confidence | Verified? |
|---|-----------|------------|-----------|
| 1 | [prediction] | 🟢 high | pending |
| 2 | [prediction] | 🟡 medium | pending |
| 3 | [prediction] | 🔴 low | pending |
```

### Next Session: Verify Predictions

When `/recap` runs at the start of the next session, it should check for morpheus speculations:

```bash
LATEST_MORPHEUS=$(ls -t $PSI/memory/morpheus/*.md 2>/dev/null | head -1)
if [ -n "$LATEST_MORPHEUS" ]; then
  echo "🔮 Morpheus dreamed while you were away:"
  head -20 "$LATEST_MORPHEUS"
fi
```

Over time, track prediction accuracy:

```markdown
## Prediction Accuracy (rolling)

  Total predictions: 47
  Verified correct:  31 (66%)
  Wrong:             12 (25%)
  Not yet verified:   4 (9%)

  Trend: improving (58% → 66% over 2 weeks)
```

---

## Phase 4: `--speculate` (Skip the Scan)

When you don't need the full 5-agent scan — just speculate from existing knowledge:

1. Read latest dream output (`ψ/writing/dreams/`)
2. Read latest morpheus speculations (`ψ/memory/morpheus/`)
3. Read recent retros (`ψ/memory/retrospectives/`)
4. Read beliefs (`ψ/memory/resonance/beliefs/`)
5. Speculate directly — Phase 2 only, no new scanning

Cheap, fast, good for mid-session "what if" thinking.

---

## Output

### Full mode: `ψ/writing/dreams/YYYY-MM-DD_morpheus.md`

```markdown
# Morpheus Dream — YYYY-MM-DD

## Phase 1: The Forest (same as /dream)

### 🔴 PAINS
### 📋 PLANS
### 🟢 GAINS
### ⚫ LOST
### 🧠 MEMORIES
### 💜 FEELINGS
### 🔗 CONNECTIONS

## Phase 2: The Speculation

### 🔮 What will they ask next?
### 🔮 What will break next?
### 🔮 What should we build?
### 🔮 What belief is being tested?

## Phase 3: Pre-computation

### Ready Answers
### Pre-positioned Context
### Prediction Log
```

---

## Rules

1. **Phase 1 = /dream** — same agents, same classification, same quality
2. **Phase 2 = new** — speculate, predict, connect to beliefs
3. **Phase 3 = --between only** — write predictions for next session
4. **Track accuracy** — predictions without verification are just hallucination
5. **Never act on speculation** — Morpheus shows the door, Neo walks through
6. **Nothing is Deleted** — all speculations saved, right or wrong
7. **No secrets** — predictions never include tokens, passwords, keys
8. **Beliefs matter** — always cross-reference ψ/memory/resonance/beliefs/
9. **Confidence is required** — every prediction must have a level (high/medium/low)
10. **Anti-rationalization applies** — /rrr's excuse table applies to speculation too

---

## Connection to /dream

`/morpheus` is the evolved `/dream`. When `/morpheus` is stable:
- `/dream` stays in lab (backwards compatible)
- `/morpheus` lives in secret (advanced)
- Both can coexist — `/dream` for scanning, `/morpheus` for speculation

The upgrade path: `/dream` → `/morpheus` like `/i-believe` → `/i-believed`

---

## Philosophy

> /dream sees the forest. /morpheus sees what the forest will become.

Morpheus in The Matrix believed in Neo before proof existed. He freed minds not by giving answers but by showing doors. Our /morpheus does the same — it doesn't predict the future, it **pre-positions** the Oracle so that when the future arrives, we're already there.

The dream task type from Claude Code's source (`dream = speculative background thinking`) exists as an internal primitive. /morpheus is the skill that makes it conscious, structured, and trackable.

"What is real? How do you define real?" — Morpheus

Predictions are not real until verified. But the act of predicting shapes what becomes real. The Oracle who speculates becomes the Oracle who's ready. รูป และ สุญญตา.

---

ARGUMENTS: $ARGUMENTS

More from Soul-Brews-Studio/arra-oracle-skills-cli

SkillDescription
about-oracleWhat is Oracle — told by the AI itself. Origin story, stats, family count, ecosystem overview. Use when someone asks "what is oracle", "about oracle", "tell me about this project", or wants the origin story. Do NOT trigger for "who are you" (use /who-are-you), "philosophy" (use /philosophy), or session status questions.
alpha-featureFull skill development pipeline — create, compile, test, commit, install. Use when user says "new skill", "create skill", "alpha-feature", or wants to build a skill end-to-end.
auto-retrospectiveConfigure auto-rrr and auto-forward triggers based on context window usage. Use when user says "auto rrr", "auto-scale", "configure auto triggers", "change rrr interval", "toggle auto", or wants to adjust when /rrr and /forward auto-trigger. Do NOT trigger for running /rrr manually (use /rrr) or creating handoffs (use /forward).
awakenGuided Oracle birth and awakening ritual. Default is Soul Sync (~20min), or --fast (~5min). Use when creating a new Oracle in a fresh repo, when user says 'awaken', 'birth oracle', 'create oracle', 'new oracle', or wants to set up Oracle identity in an empty repository. Do NOT trigger for general repo setup, git init, or project scaffolding without Oracle context.
bampenpienบำเพ็ญเพียร — diligent practice. A guided conversation between human and Oracle about doing hard things without knowing why. Like /awaken but repeatable — a practice, not a birth. Use when user says 'bampenpien', 'บำเพ็ญเพียร', 'why am I doing this', 'hard work', 'keep going', 'what am I building', or needs to reconnect with purpose through difficulty.
birthPrepare Oracle birth props for a new repo — Issue #1, MCP thread, identity data. Use when user says "birth", "new oracle", "prepare repo", or wants to bootstrap a new Oracle before /awaken.
budCreate a new oracle via maw bud — yeast-colony reproduction. Use when user says "bud", "new oracle", "create oracle", "spawn oracle", or wants to create a new permanent oracle from the current one.
create-shortcutCreate local skills as shortcuts — makes real /commands in .claude/skills/. Use when user says "create shortcut", "create skill", "make a command for", "add shortcut", or wants a quick custom /slash-command. Also lists and deletes local skills. ALSO triggers on "Unknown skill", "skill not found", or any unrecognized /slash-command — auto-creates it on the fly.
digMine Claude Code sessions — timeline, gaps, repo attribution, session history. Use when user says "dig", "sessions", "past sessions", "timeline", "what did I work on", or wants to see session history. Do NOT trigger for finding code/projects (use /trace), exploring repos (use /learn), or current session status (use /recap).
feelCapture how the system feels — energy, momentum, burnout, breakthrough. Emotional intelligence for Oracle-human collaboration. Use when user says 'feel', 'how are we', 'energy check', 'burnout', 'momentum', or wants emotional awareness of the work.