بنقرة واحدة
gsd-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
File a phase artifact into MemPalace; mirror decision facts into its temporal KG
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create detailed phase plan (PLAN.md) with verification loop
Cross-AI plan convergence - replan until review concerns are resolved.
Generate an AI-SPEC.md design contract for phases that involve building AI systems.
Start a new milestone cycle — update PROJECT.md and route to requirements
Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall
project lifecycle | milestones audits summary
| name | gsd-mempalace-capture |
| description | File a phase artifact into MemPalace; mirror decision facts into its temporal KG |
| argument-hint | [CONTEXT.md|PLAN.md|SUMMARY.md] |
| allowed-tools | ["Read","Bash"] |
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.
Before ANY tool calls, display this banner:
GSD > MEMPALACE CAPTURE
Then proceed to Step 1.
Check whether the MemPalace capability is enabled by reading .planning/config.json directly with the Read tool.
.planning/config.json with the Read tool.config.mempalace is absent, or config.mempalace.enabled !== true, or config.mempalace.capture_artifacts !== true: display the disabled message and STOP.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.
$ARGUMENTS. If absent, infer from the loop point: discuss:post → CONTEXT.md, plan:post → PLAN.md, verify:post → SUMMARY.md.CONTEXT.md → decisionsPLAN.md → planningSUMMARY.md → milestones
(Confirmed problem→fix pairs go to problems — see the capture-problems fragment used at execute:wave:post.)config.mempalace.wing if non-empty, else config.project_code, else the repo directory name.config.mempalace.memory_mode. Prefer MCP (mempalace_*) when your MemPalace MCP server is registered and your runtime permits those tools; otherwise use the mempalace CLI (covered by this skill's Bash allow-tool), as in mempalace-recall.On any error or timeout, stop and let the phase continue -- capture is best-effort.
Dedup first. Interactive: mempalace_check_duplicate on the artifact's deterministic drawer id. Headless: rely on mempalace mine's content-hash idempotency.
Add the drawer (verbatim). File the exact artifact text into room: <room> of wing: <wing> with provenance (source_file, phase id). Interactive: mempalace_add_drawer. Headless: see below.
mempalace mine has no --room flag — only search accepts --room (CLI reference: https://mempalaceofficial.com/reference/cli.html). Room assignment is driven by detect_room() matching folder-path segments against the rooms: list in mempalace.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 so detect_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 when config.mempalace.mirror_kg is true: extract decision/delivery facts and mempalace_kg_add them with valid_from = the phase date (e.g. (<project>, decided, <decision>) from CONTEXT; (<phase>, delivered, <capability>) from SUMMARY). Under augment these are an additive mirror of GSD's native .planning/graphs/. Under kg_backend/replace the 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).
Print a one-line summary: Filed <artifact> → <wing>/<room> (<n> KG facts) or MemPalace unavailable — capture skipped.
onError: skip.sync --apply) is the curator agent's job at ship:post, wing-scoped only.