beo-dream

Consolidate codex-derived learnings into .beads/learnings with provenance checks.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/minhtri2710/skills --skill beo-dream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beo-dream
Source: https://github.com/minhtri2710/skills/tree/main/skills/beo/dream
Command: npx skills add https://github.com/minhtri2710/skills --skill beo-dream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates codex-derived learnings into a stable, durable knowledge store under .beads/learnings, reducing drift and enabling governance over prior decisions.

Core Features & Use Cases

  • Performs a single manual consolidation pass to update learnings with provenance-aware mode (bootstrap or recurring) and a controlled write surface.
  • Enforces safety, redaction, and governance rules (no edits to critical-patterns.md without explicit approval; secrets/PII redacted before summaries or writes).
  • Keeps the durable knowledge focused in .beads/learnings/*.md and integrates with the knowledge-store protocol via references/knowledge-store.md.

Quick Start

Run a manual dream consolidation pass to refresh and lock in durable learnings across the current feature set, using the default 30-day staleness window unless overridden.

Frequently Asked Questions about beo-dream

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

FAQPage Schema
How do I consolidate learnings into a durable knowledge store?

Consolidating learnings requires a manual consolidation pass that writes durable knowledge into the .beads/learnings store, applying provenance checks and governance rules to determine whether to update or create new entries.

What is the best way to prevent knowledge drift when consolidating feature learnings?

To prevent knowledge drift, use a recurring consolidation mode with a default 30-day staleness window, ensuring prior decisions are refreshed, locked in, and governed within the durable knowledge store.

How does redaction work when persisting learnings to a knowledge store?

Redaction automatically scrubs secrets and PII from learnings before summaries are generated or writes are persisted, ensuring sensitive data never enters the .beads/learnings markdown files.

Can I edit critical patterns without approval during the learning consolidation process?

Editing critical patterns requires explicit approval, as the consolidation process enforces a critical-patterns approval gate to prevent unauthorized modifications to governed knowledge entries.

When do I need bootstrap mode versus recurring mode for learning consolidation?

Bootstrap mode is needed for initial knowledge store setup, while recurring mode handles subsequent consolidation passes with a 30-day staleness window to refresh and update existing learnings.

Does the knowledge store protocol integrate with existing markdown learnings files?

The knowledge store protocol integrates via references/knowledge-store.md, keeping durable knowledge focused in .beads/learnings markdown files while persisting run provenance after each consolidation pass.