Menu
Access, search, and manage the team memory nexus — mine projects, store context, and recall knowledge. Triggers on "remember this", "save to memory", "check memory", "what do we know about", "recall". Auto-triggers at session start to load context.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | memory |
| description | Access, search, and manage the team memory nexus — mine projects, store context, and recall knowledge. Triggers on "remember this", "save to memory", "check memory", "what do we know about", "recall". Auto-triggers at session start to load context. |
Team memory nexus — organize knowledge as wings → rooms → drawers, searchable semantically via MemPalace.
Ensure mempalace is installed:
mempalace --version
If not installed:
uv tool install mempalace # recommended
# or: pip install mempalace
Call mempalace_status at the start of every session to orient. For deeper context, search the relevant wing.
Save to the nexus when the user shares:
Use mempalace_add_drawer with appropriate wing and room.
work — project code, decisions, architecturepersonal — individual preferences, notesteam — shared team knowledge, onboarding/memory-search — semantic search across the nexus/memory-mine — mine a project directory or text into the nexus/memory-status — nexus stats and structureUse when bootstrapping a repository — greenfield or brownfield — into Uhstray's standard development conventions, OpenSpec, and the two-store memory setup. Idempotent and non-destructive: safe to re-run, never overwrites existing docs. Triggers on "repo kickstart", "bootstrap this repo", "set up our conventions", "conform this repo", "initialize plans/openspec/memory", "initialize this repo for openspec and memory", "set up two-store memory here", "index this repo and create its memory bank".
Use when checking or setting up the four-strata memory system on this machine and in the current project — "is my memory set up right", "memory onboarding", "set up memory", "check my memory setup", after a fresh machine/repo, when repo-kickstart or buhhdy's preflight reports memory degradation, or when .claude/memory / MemPalace / evolve looks misconfigured.
Use when any orchestrating agent's development workflow — buhhdy's Workflow 2 is the canonical caller — has open PRs that need driving from creation through merge and cleanup — the terminal step once PRs are open. Triggers on "shepherd this PR", "drive the PR to merge", "babysit the PRs", "monitor the PR to merge", and post-merge close-out (close linked issues, archive the change, remove the worktree, janitor stale branches in the orchestrator's own prefix (buhhdy/* canonical)). Also load to verify PR-lifecycle preconditions (branch protection, CodeRabbit) before shepherding.
Use when the user says "remember", "don't forget", "save that", "keep that in mind", "recall", "what do we know about", "look that up", or any request to persist or retrieve project knowledge — stores memories in .claude/memory/ using the Claude Code memory format, committed to git so the whole team shares context.
Use when starting new planning/research on a project or picking up development against an existing plan — buhhdy's two standard, repeatable sequences: Planning & Research (fresh problem to a validated plan — an OpenSpec change where the repo has adopted the conventions — plus issues) and Development (fanout, audit, docs, and pr-shepherd).
Reference skill for buhhdy's provider routing logic — the decision tree, model tier table, per-provider strengths, skill-to-provider affinity, and cross-review pairings. Load when reasoning about which provider to use and why, or when a task doesn't clearly match the main routing tree.