Extension ID

memory

Extension Name

Spec Kit Memory

Version

0.3.0

Description

Recalls prior specs and decisions from configurable memory tools (e.g. memsearch) before SDLC stages, so planning and specification start from what the project already knows instead of a blank page.

Author

Andrey Zaytsev

Repository URL

https://github.com/zaytsevand/spec-kit-memory

Download URL

https://github.com/zaytsevand/spec-kit-memory/archive/refs/tags/v0.3.0.zip

License

MIT

Homepage (optional)

https://github.com/zaytsevand/spec-kit-memory

Documentation URL (optional)

https://github.com/zaytsevand/spec-kit-memory/blob/main/README.md

Required Spec Kit Version

=0.2.0

Required Tools (optional)

• The set of memory tools is a config list, not a hardcoded dependency — the extension invokes whatever recall commands/skills the agent already has.
• memsearch (memory-recall) — optional; the reference backend used in the default config. Any plugin:skill or registered speckit command works in its place.
• Recall is fail-open: if no memory tool is configured or a tool errors/returns nothing, the stage proceeds uninterrupted.

Number of Commands

2

Number of Hooks (optional)

3

Tags

memory, recall, research, memsearch

Key Features

• Prior-art recall before you write — fires on before_specify (primary point) and before_plan, handing a short Prior art summary to each stage.
• Configurable memory-tool list — point it at memsearch or any recall command/skill; results are run in order and merged.
• Read-only recall — the recall command never writes specs, plans, or code.
• Keyword distillation + clustering — derives keywords from the feature (title, domain nouns, entities, FR terms, branch slug), clusters them into thematic groups (capped), and runs one recall pass per group.
• ## Related specs (from memory) writer — speckit.memory.list-related-specs runs on after_plan and writes a compact, idempotent related-specs section (id + title) into the feature's research.md.
• Fail-open by design — never blocks an SDLC stage when a tool is missing, errors, or finds nothing.

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on: the LinkedInTools monorepo (Django webapp + desktop client, spec-driven development), where this extension has been installed as a --dev local extension (specify extension add --dev) and exercised across dozens of features. specify extension list reports ✓ Spec Kit Memory (v0.3.0) — 2 commands, 3 hooks.

Test scenarios:

1. Both commands run without error: speckit.memory.recall (on before_specify / before_plan) and speckit.memory.list-related-specs (on after_plan).
2. recall surfaces prior-art summaries into specify/plan stages; verified read-only (no spec/plan/code writes).
3. list-related-specs writes an idempotent ## Related specs (from memory) section into research.md; re-running does not duplicate it.
4. Fail-open verified: with no reachable memory tool, stages proceed uninterrupted.

Release archive: the v0.3.0 download URL above returns HTTP 200 and unpacks to a well-formed extension (extension.yml, README.md, LICENSE, commands/recall.md, commands/list-related-specs.md, config template).

Note on install path: the supported install today is the --dev local path (validated above), plus the release archive verified as downloadable and well-formed. Catalog install (specify extension add memory) becomes available once this catalog entry is accepted.

Example Usage

# Install (dev/local path — supported today)
git clone https://github.com/zaytsevand/spec-kit-memory
cd <your-speckit-project>
specify extension add --dev /path/to/spec-kit-memory
specify extension list      # ✓ Spec Kit Memory (v0.3.0) — 2 commands, 3 hooks

# After this catalog entry is accepted:
specify extension add memory --from https://github.com/zaytsevand/spec-kit-memory/archive/refs/tags/v0.3.0.zip

# Recall auto-runs on before_specify / before_plan; related-specs on after_plan.
# Configure which tools & stages in .specify/extensions/memory/memory-config.yml

Proposed Catalog Entry

{
  "memory": {
    "name": "Spec Kit Memory",
    "id": "memory",
    "description": "Recalls prior specs and decisions from configurable memory tools (e.g. memsearch) before SDLC stages, so planning and specification start from what the project already knows.",
    "author": "Andrey Zaytsev",
    "version": "0.3.0",
    "download_url": "https://github.com/zaytsevand/spec-kit-memory/archive/refs/tags/v0.3.0.zip",
    "repository": "https://github.com/zaytsevand/spec-kit-memory",
    "homepage": "https://github.com/zaytsevand/spec-kit-memory",
    "documentation": "https://github.com/zaytsevand/spec-kit-memory/blob/main/README.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.2.0"
    },
    "provides": {
      "commands": 2,
      "hooks": 3
    },
    "tags": ["memory", "recall", "research", "memsearch"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-07-10T00:00:00Z",
    "updated_at": "2026-07-10T00:00:00Z"
  }
}

Additional Context

This is a new submission (not an update to an existing entry). The extension wires Spec Kit's command-scoped hook seams (before_specify / before_plan / after_plan) to a configurable set of memory/recall tools rather than hardcoding one backend — the design goal is that any project can plug in its own recall stack.