beo-dream
Installation
SKILL.md
beo-dream
Purpose
Consolidate cross-feature learning.
Primary owned decision
Decide whether accepted feature evidence supports a shared learning update or an explicit non-promotion.
Ownership predicate
- At least two accepted features support the same shared learning candidate.
- The user explicitly requests corpus-level consolidation. "User explicitly requests corpus-level consolidation" means a direct named request in the current task or a fresh handoff with explicit corpus consolidation authorization; it does not include inferred intent from go-mode or approval context.
- Existing shared learning guidance needs consolidation from accepted feature records only when the consolidation threshold is met.
- A single-feature case is in scope only when the user explicitly asks for corpus-level analysis.
Writable surfaces
- Shared learning guidance surfaces explicitly approved by the user. When approval grants shared-guidance mutation, write to the user-confirmed target file path only. Do not infer a canonical shared guidance location; if no target path has been confirmed, surface the path choice to the user before writing.
- Consolidation records described by canonical learning doctrine.
- Shared state/handoff fields allowed by
beo-reference → skill-contract-common.md.