dream

Consolidates Claude Code session history into scored, tiered memory updates with approval gates.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill dream-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dream
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/dream
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill dream-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running projects accumulate knowledge across many Claude Code sessions, but that knowledge stays buried in conversation history while memory files grow stale, duplicated, or contradictory. This Skill runs a structured consolidation pass that reads sessions, scores knowledge candidates, and applies governed updates to memory files. ## Core Features & Use Cases - Session-driven knowledge extraction: Searches conversations with keyword queries to capture decisions, fixes, failures, patterns, and architecture choices since the last run. - Confidence scoring and lifecycle operations: Scores each entry (0.0–1.0) and proposes ADD, UPDATE, DELETE, PROMOTE, or DEMOTE operations with full justification blocks. - Tiered approval workflow: Auto-applies low-risk changes, shows diffs for medium-risk edits, and requires explicit human approval for CLAUDE.md changes and permanent deletions. - Audit trail and safety guards: Writes an append-only dream log, maintains a concurrency lock, enforces token budgets, and harvests framework facts into migration knowledge stacks. - Use Case: After two weeks of development sessions, run /dream to extract the conventions and decisions your team made, promote the durable ones into topic memory files, and prune stale entries — all with reviewable diffs. ## Quick Start Type /dream to run a memory consolidation pass over your recent Claude Code sessions and review the proposed memory updates.

Frequently Asked Questions about dream

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

FAQPage Schema
How do I consolidate Claude Code session history into memory files?

Run /dream to start a consolidation pass. It searches recent conversations with keyword queries, extracts durable knowledge like decisions and fixes, scores each candidate, and proposes ADD, UPDATE, or DELETE operations for your approval before writing.

What is the difference between MEMORY.md and topic files in Claude memory?

MEMORY.md is a lightweight inbox for manual notes and auto-captured entries, while topic files (memory/topic-*.md) hold consolidated, durable knowledge. The dream run processes MEMORY.md entries into topic files and removes them from the inbox to keep it lean.

Can /dream modify CLAUDE.md automatically?

No. PROMOTE and DEMOTE operations that write to or remove from CLAUDE.md are always Tier 3, requiring explicit per-item human approval regardless of confidence score. CLAUDE.md is treated as a hard boundary.

What happens if two /dream runs execute at the same time?

A concurrency lock file (memory/.dream-lock) prevents parallel runs. If a lock exists, the run stops with a warning; concurrent runs would otherwise overwrite memory files with no merge, silently losing one run's changes.

Why does /dream stop with a token budget warning?

When combined memory and session context exceeds roughly 80K tokens, the run halts to avoid unsafe consolidation. Archive older topic files first or rerun with a narrower keyword to process one topic area at a time.

How does confidence scoring decide which memory entries to delete?

Entries start from base scores (0.65 session-sourced, 0.70 auto-capture), gain bonuses for confirming sessions, and decay 0.1 per unreferenced cycle. Entries at or below 0.2 that were not referenced become DELETE candidates, subject to human approval.