gsd-mempalace-capture
Skill1 starsChanged 58 days agoMITView on GitHub
File a phase artifact into MemPalace; mirror decision facts into its temporal KG
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- open-gsd/get-shit-done-reduxedited, first seen Oct 8, 2026
- open-gsd/gsd-coreedited, first seen Sep 2, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- open-gsd/get-shit-done-redux★ 11k85% same
- open-gsd/gsd-core★ 11k85% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ask-mattSkill
- banner-designSkill
- brandSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- designSkill
- design-systemSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- git-guardrails-claude-codeSkill
- graphifySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- gsd-add-testsSkill
- gsd-ai-integration-phaseSkill
- gsd-audit-fixSkill
- gsd-audit-milestoneSkill
- gsd-audit-uatSkill
- gsd-autonomousSkill
- gsd-captureSkill
- gsd-cleanupSkill
- gsd-code-reviewSkill
- gsd-complete-milestoneSkill
- gsd-configSkill
- gsd-debugSkill
- gsd-discuss-phaseSkill
- gsd-docs-updateSkill
- gsd-eval-reviewSkill
- gsd-execute-phaseSkill
- gsd-exploreSkill
- gsd-extract-learningsSkill
- gsd-fastSkill
- gsd-forensicsSkill
- gsd-graphifySkill
- gsd-healthSkill
- gsd-helpSkill
- gsd-importSkill
- gsd-inboxSkill
- gsd-ingest-docsSkill
- gsd-managerSkill
- gsd-map-codebaseSkill
- gsd-mempalace-recallSkill
- gsd-milestone-summarySkill
- gsd-mvp-phaseSkill
- gsd-new-milestoneSkill
- gsd-new-projectSkill
- gsd-nextSkill
- gsd-ns-contextSkill
- gsd-ns-ideateSkill
- gsd-ns-manageSkill
- gsd-ns-projectSkill
- gsd-ns-reviewSkill
- gsd-ns-workflowSkill
- gsd-onboardSkill
- gsd-pause-workSkill
- gsd-phaseSkill
- gsd-plan-phaseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Check whether the MemPalace capability is enabled by reading .planning/config.json directly with the Read tool.
- Very specific: line 22
Read .planning/config.json with the Read tool.
- Very specific: line 23
If the file does not exist, or config.mempalace is absent, or config.mempalace.enabled !== true, or config.mempalace.capture_artifacts === …
- Very specific: line 46
Mode / transport: Read config.mempalace.memory_mode.
- Very specific: line 93
DO NOT let any MemPalace error fail the step -- capture is onError: skip.
- Distinctive: line 94
DO NOT write lossy summaries -- store the verbatim artifact text (AAAK compression is a separate, optional index).
- Very specific: line 95
DO NOT prune or delete drawers here -- pruning (sync --apply) is the curator agent's job at ship:post, wing-scoped only.
- Distinctive: line 96
DO NOT skip the config gate or the dedup check.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by the command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.
Step 0 -- Banner
Before ANY tool calls, display this banner:
GSD > MEMPALACE CAPTUREThen proceed to Step 1.
Step 1 -- Config Gate
Check whether the MemPalace capability is enabled by reading .planning/config.json directly with the Read tool.
- Read
.planning/config.jsonwith the Read tool. - If the file does not exist, or
config.mempalaceis absent, orconfig.mempalace.enabled !== true, orconfig.mempalace.capture_artifacts === false: display the disabled message and STOP. - Otherwise proceed to Step 2.
Disabled message:
GSD > MEMPALACE CAPTURE
MemPalace capture is disabled (mempalace.enabled / mempalace.capture_artifacts).
Nothing was filed; the loop proceeds normally.This step is onError: skip at discuss:post / plan:post / verify:post -- capture never fails a phase.
Step 2 -- Resolve target
- Artifact. Take the artifact from
$ARGUMENTS. If absent, infer from the loop point:discuss:post→CONTEXT.md,plan:post→PLAN.md,verify:post→SUMMARY.md. - Room. Map artifact → room:
CONTEXT.md→decisionsPLAN.md→planningSUMMARY.md→milestones(Confirmed problem→fix pairs go toproblems— see thecapture-problemsfragment used atexecute:wave:post.)
- Wing.
config.mempalace.wingif non-empty, elseconfig.project_code, else the repo directory name. - Mode / transport. Read
config.mempalace.memory_mode. Prefer MCP (mempalace_*) when your MemPalace MCP server is registered and your runtime permits those tools; otherwise use themempalaceCLI (covered by this skill'sBashallow-tool), as inmempalace-recall.
Step 3 -- File verbatim (idempotent)
On any error or timeout, stop and let the phase continue -- capture is best-effort.
- Dedup first. Interactive:
mempalace_check_duplicateon the artifact's deterministic drawer id. Headless: rely onmempalace mine's content-hash idempotency. Add the drawer (verbatim). File the exact artifact text into
room: <room>ofwing: <wing>with provenance (source_file, phase id). Interactive:mempalace_add_drawer. Headless: see below.mempalace minehas no--roomflag — onlysearchaccepts--room(CLI reference: https://mempalaceofficial.com/reference/cli.html). Room assignment is driven bydetect_room()matching folder-path segments against therooms:list inmempalace.yaml(mining guide: https://mempalaceofficial.com/guide/mining.html — "Rooms are auto-detected from your folder structure"; config reference: https://mempalaceofficial.com/guide/configuration.html). Stage the artifact under a room-named folder sodetect_room()assigns it correctly:STAGE=".planning/.mempalace-stage" # One-time: declare the GSD room taxonomy so detect_room() recognizes these folders mkdir -p "$STAGE" [ -f "$STAGE/mempalace.yaml" ] || cat > "$STAGE/mempalace.yaml" <<'YAML' # Each entry MUST be a dict with a `name` key (the miner's detect_room() # indexes room["name"] — a bare-string list crashes _mine_impl with # TypeError: string indices must be integers, not 'str'). Optional fields: # `description`, `keywords` (matched against folder-path segments). rooms: - name: decisions - name: planning - name: milestones - name: problems - name: general YAML # Suppress MemPalace cache artifacts written into the scanned tree [ -f "$STAGE/.gitignore" ] || echo "mempalace_embedder.json" > "$STAGE/.gitignore" # Stage under <room>/<phase-id>/<basename> — stable path so mine's content-hash # idempotency (file_already_mined keys on absolute source_file + mtime) deduplicates # instead of creating duplicate drawers on re-runs. ROOM_DIR="$STAGE/<room>/<phase-id>" mkdir -p "$ROOM_DIR" cp "<artifact-path>" "$ROOM_DIR/<basename>" # Mine with --wing only — no --room flag; detect_room() assigns from the folder path mempalace mine "$STAGE" --wing <wing>- Mirror KG facts unless
config.mempalace.mirror_kg === false(registry default is true — an absent key means enabled): extract decision/delivery facts andmempalace_kg_addthem withvalid_from= the phase date (e.g.(<project>, decided, <decision>)from CONTEXT;(<phase>, delivered, <capability>)from SUMMARY). Underaugmentthese are an additive mirror of GSD's native.planning/graphs/. Underkg_backend/replacethe palace KG is the authoritative fact store — GSD still produces.planning/graphs/through its normal graphify, so an unreachable palace never loses a fact. - Re-running a phase MUST NOT create duplicate drawers (deterministic ids +
check_duplicate).
Step 4 -- Report
Print a one-line summary: Filed <artifact> → <wing>/<room> (<n> KG facts) or MemPalace unavailable — capture skipped.
Anti-Patterns
- DO NOT let any MemPalace error fail the step -- capture is
onError: skip. - DO NOT write lossy summaries -- store the verbatim artifact text (AAAK compression is a separate, optional index).
- DO NOT prune or delete drawers here -- pruning (
sync --apply) is the curator agent's job atship:post, wing-scoped only. - DO NOT skip the config gate or the dedup check.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

