Stats
Actions
Tags
From stratosphere-os
End-of-day maintenance routine to reconcile multi-session learnings and purge intermediate scratchpads.
How this command is triggered — by the user, by Claude, or both
Slash command
/stratosphere-os:0d_nightly-consolidationThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Nightly Consolidation ## Constraint Do not modify any files without explicit user approval. ## Phase 1: Review Sessions - Review all sessions across all models from the last 24 hours. - Identify problems, inefficiencies, redundant tool calls, and recurring main/sub-agent mistakes worth optimizing. ## Phase 2: Distill Plan - Output a high-density, bulleted proposal in `.tmp/` for how sessions can be optimized or which skills/workflows to modify. - Name the plan file `nightly_[date].md`. ## Phase 3: Crystallize Memory - Scan all entries in `.memory/*` except `DESIGN.md` (external Googl...
Do not modify any files without explicit user approval.
.tmp/ for how sessions can be optimized or which skills/workflows to modify.nightly_[date].md.Scan all entries in .memory/* except DESIGN.md (external Google Labs DESIGN.md spec) for:
| Trigger | Proposal |
|---|---|
| Duplicate or overlapping entries | Merge? |
[PATTERN] cited ≥3 times across tasks | Promote to [LAW] in ARCHITECTURE.md or DESIGN_RULES.md? (not applicable to GLOSSARY.md) |
[ASSUMED] older than 5 sessions, never validated | Delete? |
If proposals surface adjust the plan created in Phase 2. If nothing qualifies, skip silently.
Halt execution entirely. Ask the user: "What aspects of the plan do you want to implement?"
npx claudepluginhub patn-git/stratosphere-os --plugin stratosphere-os