speckit-memory-md-init

name	speckit-memory-md-init
description	Initialize layered memory, synthesis, and spec starter files in a target repo.
compatibility	Requires spec-kit project structure with .specify/ directory
metadata	{"author":"github-spec-kit","source":"memory-md:commands/speckit.memory-md.init.md"}

Init

Set up this repository to use the layered Spec Kit Memory workflow.

Tasks:

1. Read config-template.yml at the extension root for default values. If the project has .specify/extensions/memory-md/config.yml, use those values instead. Fall back to defaults: memory_root: docs/memory, specs_root: specs.
2. Ask whether the project wants the optional SQLite optimizer enabled. Explain the minimum requirements first: Node.js 18+, npm, local filesystem access, and the ability to install the better-sqlite3 native dependency if a prebuilt binary is not available. If the user says no, keep the markdown-first workflow only. If the user says yes, set optimizer.enabled: true in .specify/extensions/memory-md/config.yml, and then automatically prepare the local optimizer by running npm install && npm run build inside the .specify/extensions/memory-md directory using the terminal. If the npm install or npm run build fails (e.g. due to missing prerequisites), explain exactly what is missing, provide them the manual commands (cd .specify/extensions/memory-md && npm install && npm run build), and then continue with markdown-first mode.
3. Ensure these folders exist:
   • {memory_root} (default: docs/memory)
   • {specs_root} (default: specs)
   • .github
4. Create missing durable memory files from the extension templates:
   • {memory_root}/INDEX.md
   • {memory_root}/PROJECT_CONTEXT.md
   • {memory_root}/ARCHITECTURE.md
   • {memory_root}/DECISIONS.md
   • {memory_root}/BUGS.md
   • {memory_root}/WORKLOG.md
5. Create or update spec starter files so every feature folder can contain:
   • spec.md
   • plan.md
   • tasks.md
   • {feature_memory_filename} (default: memory.md)
   • {memory_synthesis_filename} (default: memory-synthesis.md)
6. Centralize Memory Governance:
   • Mandatory: Create or Update .specify/memory/workflow.md. If the file already exists, reconcile its content with the extension template to ensure it contains the latest mandatory command references, while strictly preserving any existing project-specific governance rules.
   • Migration: Detect active agent context files: .github/copilot-instructions.md, AGENTS.md, CLAUDE.md, GEMINI.md, and Windsurf rules.
   • Inject Pointer: For each existing file, do NOT overwrite the whole file. Instead, find the ### Spec Kit section (or create it) and replace it with the Pointer Model: "You MUST follow the memory-first workflow defined in .specify/memory/workflow.md and proactively execute /speckit.memory-md.prepare-context before planning."
7. If .specify/extensions/memory-md/config.yml does not exist, create it from config-template.yml with default values.
8. Summarize the memory model:
   • constitution / principles = stable operating rules
   • durable project memory = reusable cross-feature knowledge
   • active feature memory = feature-local constraints, open questions, and carry-forward context
   • memory index = compact routing map for selecting relevant durable entries
   • ephemeral run context = temporary prompt or terminal state that must not be committed

Guardrails:

• Safety First: Update existing files safely by targeting only managed sections (e.g., ### Spec Kit).
• No Destruction: Never overwrite project-specific memory or custom agent instructions without explicit approval.
• Reconciliation: If .specify/memory/workflow.md exists, treat it as a "living document"—improve its technical requirements without deleting its existing context.

9. List the first customization steps:
   • fill in project context and architecture
   • migrate any durable lessons into decisions or bugs
   • stop using worklog as a changelog
   • use feature memory plus synthesis on the next spec
   • review config.yml and adjust paths if needed

Prioritize preserving existing project files. Never overwrite project-specific memory without explicit approval.