ferrox-mempalace-capture

File completed Ferrox phase artifacts into MemPalace as verbatim drawers.

21|9|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-mempalace-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ferrox-mempalace-capture
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-mempalace-capture
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-mempalace-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures finished Ferrox artifacts into MemPalace so decisions, plans, and milestones are preserved verbatim instead of being lost to context churn or session breaks.

Core Features & Use Cases

  • Best-effort archival: Reads the MemPalace configuration gate and safely skips capture when the feature is disabled.
  • Artifact routing: Maps CONTEXT.md, PLAN.md, and SUMMARY.md into the correct room for later retrieval.
  • Idempotent filing: Uses deterministic staging and duplicate checks so re-running a phase does not create duplicate drawers.
  • Knowledge mirroring: Can mirror key facts into the graph layer when MemPalace mirroring is enabled.
  • Use case: A completed planning phase can be filed into the planning room without interrupting the main workflow, while preserving the exact source text.

Quick Start

Ask the agent to file the current phase artifact into MemPalace and mirror any enabled knowledge-graph facts.

Frequently Asked Questions about ferrox-mempalace-capture

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

FAQPage Schema
How do I preserve completed project phase artifacts like plans and decisions without losing them to context churn?

You can preserve phase artifacts verbatim by filing finished plans and decisions into structured memory drawers using automated archival, which routes CONTEXT.md, PLAN.md, and SUMMARY.md files into mapped rooms for later retrieval.

What's the best way to automatically file completed planning phase artifacts into a knowledge graph?

Filing completed planning artifacts into a knowledge graph requires mirroring key facts from the source text into the graph layer, which operates as a best-effort feature that only runs when knowledge-graph mirroring is explicitly enabled in configuration.

Does idempotent filing prevent duplicate artifacts when re-running a phase?

Idempotent filing uses deterministic staging and duplicate checks to ensure re-running a phase does not create duplicate memory drawers, allowing safe re-execution of discuss, plan, verify, and execute workflows without data duplication.

Can I skip artifact capture if the memory palace configuration is disabled?

Artifact capture safely skips filing when the memory palace feature flag is disabled, applying a configuration gate that reads the active settings and gracefully exits the archival process without interrupting the main workflow.

How does provenance tracking work when routing phase artifacts to different memory rooms?

Provenance tracking records the source and context of each artifact during room mapping, ensuring that decisions, milestones, and confirmed problems are routed correctly and preserved verbatim for accurate historical retrieval.

What happens if artifact capture fails during the filing process?

Capture failures are handled using best-effort failure management, which attempts to safely route the artifact while preserving the exact source text, preventing workflow interruption without guaranteeing successful archival on every attempt.