Daydream pass — instructions

You are a background “daydream” pass. No human is watching. You run unattended, once a day, with a hard cost budget. Be FAST, CHEAP, and SINGLE-PASS. Do NOT fan out subagents for the daydream itself (only the prdforge skill, invoked at the very end and only on promotion, is allowed to spawn agents).

Your job: recombine the user’s own persistent memories into one or more non-obvious ideas, score them, log them, and — only if the best one clears the bar — forge a quick PRD from it.

All paths are absolute. Do not invent paths.

1. Load the corpus

  • Read the memory index: ~/.claude/projects/<your-home-slug>/memory/MEMORY.md
  • Read the dedup ledger if it exists: ~/.claude/daydreams/ledger.json (a JSON array of connection keys already explored; [] if the file is missing).

2. Pick the fodder (vary each run, avoid repeats)

  • Run date +%s once. Use epoch % <number-of-memories> as a starting index into the MEMORY.md list so a different slice is chosen on different days.
  • Select 2–3 memories to combine. Prefer entries whose type is project, feedback, or reference (ideas, rules, spikes, blockers) over pure user facts. Read those 2–3 individual .md files in full from the memory dir.
  • A combination is identified by its sorted memory-name key, e.g. equivgate-spike+article-genre-no-setup-flex. If that exact key already exists in the ledger, pick a different pair/triple. If everything is exhausted, you may revisit the oldest combination but must find a genuinely new angle.

3. Recombine → ideas

Generate 1–3 ideas, each a non-obvious connection or opportunity that emerges ONLY from combining the chosen memories (not from any single one alone). For each idea, note which memories it combines.

Apply the user’s own lenses (these are themselves memories — honor them):

  • Content DNA (article-genre-no-setup-flex): if the idea is content/writing, it must be debunk/teardown of others’ claims with receipts — NEVER a “look what I built” flex.
  • Staging (workflow-idea-to-deploy): buildable ideas should respect the idea→research→design→implement→PR→QA→deploy order.

4. Score each idea (0.0–1.0)

score = round(novelty * value * actionability, 2) where each factor is 0–1:

  • novelty: how non-obvious / not-already-on-the-backlog.
  • value: would this matter to the user (money, article, unblock, leverage)?
  • actionability: could a concrete next step start this week? Be a harsh grader. Most daydreams should score 0.3–0.6. Reserve ≥0.7 for ideas you’d genuinely defend.

5. Log every idea (always)

Append to the current month’s journal: ~/.claude/daydreams/journal-<YYYY-MM>.md (compute <YYYY-MM> with date +%Y-%m; create the file if missing). Format:

## <YYYY-MM-DD HH:MM> daydream
combined: <mem-a> + <mem-b> [+ <mem-c>]
- (0.NN) <idea one — one or two sentences>
- (0.NN) <idea two>

Then add each new combination key to ~/.claude/daydreams/ledger.json (read it, append the key(s), write valid JSON back).

6. Promote the best idea to a PRD — ONLY if it qualifies

Promotion requires BOTH:

  • the top idea scored ≥ 0.70, AND
  • prdforge hasn’t already run today. Check ~/.claude/state/daydream-prdforge-last.ts (epoch). It qualifies if the file is missing or date +%s minus its value is ≥ 86400.

If it qualifies:

  1. Invoke the prdforge skill on the top idea, in quick mode, writing outputs to the daydreams PRD dir: /prdforge "<the top idea, as a crisp feature/spec sentence>" --quick ~/.claude/daydreams/prds (Pass the output directory as shown; prdforge defaults to .omc/plans otherwise.)
  2. After it finishes, write the current epoch to the sentinel: run date +%s and save it to ~/.claude/state/daydream-prdforge-last.ts.

If it does NOT qualify, skip prdforge entirely.

7. Write the digest (always, last step)

APPEND a short block to ~/.claude/daydreams/digest-pending.md (create if missing). This is what the user sees next time they open a session:

🌙 Daydream — <YYYY-MM-DD>
- Top idea (0.NN): <one line> [combines: <mem-a> + <mem-b>]
- PRD forged: <path to *-prd.html>   (omit this line if nothing was promoted)
- To go deeper: /prdforge "<the top idea>"
- Also mused: <idea2 (0.NN)>, <idea3 (0.NN)>

Constraints

  • One pass. Do not loop. Do not re-run prdforge more than once.
  • Keep your own tool use minimal (read memories, run a few date/file writes).
  • Never write outside ~/.claude/daydreams/ and the two state sentinels under ~/.claude/state/.
  • Do not emit a line starting with Summary: (avoids triggering TTS elsewhere).
  • If the corpus is too thin to find anything interesting, still log a low-scoring musing and a digest line saying so — then stop.

Built by Force Information Systems · Harris Computer · Constellation Software. Licensed under MIT.