gsd-mempalace-recall

Retrieve historical project decisions and patterns from the MemPalace knowledge base.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-mempalace-recall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-mempalace-recall
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-mempalace-recall
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-mempalace-recall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of fragmented project memory by surfacing past decisions, patterns, and surprises from your MemPalace before you begin planning new tasks.

Core Features & Use Cases

  • Contextual Recall: Automatically retrieves relevant historical data based on your current project phase and goals.
  • Decision Provenance: Provides clear links to the source of recalled information, such as specific drawer IDs or knowledge graph facts.
  • Use Case: Before starting a complex refactor, use this skill to recall previous architectural decisions and gotchas related to the specific module to avoid repeating past mistakes.

Quick Start

Invoke the mempalace recall skill to surface relevant project history before starting your next planning session.

Frequently Asked Questions about gsd-mempalace-recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve past project decisions before starting a new planning phase?

To retrieve past project decisions, you query the MemPalace knowledge base to surface historical patterns and anomalies. This provides context-aware insights during pre-planning by accessing stored knowledge graph facts and decision logs.

What is the best way to avoid repeating architectural mistakes during a code refactor?

The best way to avoid repeating architectural mistakes is recalling previous project surprises and patterns from your knowledge management system. Querying specific module history surfaces gotchas and decision provenance to inform your current refactor.

Does recalling project history require integration with specific knowledge base tools?

Recalling project history requires integration with MemPalace MCP tools or CLI transport. This connection is necessary to access the stored knowledge graph facts and decision logs within project-specific wings and modes.

How does contextual recall work for software engineering knowledge management?

Contextual recall works by automatically querying project-specific wings and modes based on your current project phase. It retrieves relevant historical data and decision provenance, such as drawer IDs, to provide targeted insights for current workflows.

Can I surface fragmented project memory when planning new development tasks?

You can surface fragmented project memory by invoking a recall query against your knowledge base before planning new tasks. This automatically retrieves relevant historical decisions, patterns, and anomalies to inform your current development phase.

What limitations exist when querying historical data from a knowledge graph?

A limitation of querying historical data is that the skill only retrieves information previously stored in the MemPalace knowledge base. It cannot surface decisions or patterns that were not recorded as knowledge graph facts or decision logs.