factory-memory-cache

Cache project artifacts with write-through validation for Myrmion AI Factory agents.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-memory-cache
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-memory-cache
Source: https://github.com/e2its/myrmion-AI-factory/tree/main/.claude/skills/factory-memory-cache
Command: npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-memory-cache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Myrmion AI Factory agents repeatedly read the same project artifacts across sequential commands, creating redundant I/O overhead that slows down workflow execution and wastes compute resources.

Core Features & Use Cases

  • Unified Cross-Command Caching: Leverages VS Code Copilot's /memories/repo/ system to store frequently accessed data like feature states, BVL verification commands, codebase inventory indexes, and execution plans for reuse across all agent commands.
  • Consistent Data Guarantees: Implements write-through caching with source hash validation to ensure cached data never goes stale, plus graceful degradation that falls back to direct file reads if the cache is unavailable or corrupted.
  • Use Case: When running multiple IMPLEMENT --build commands for a feature, the cache eliminates repeated parsing of the codebase inventory and governance snapshot, cutting build preparation time significantly for large projects.

Quick Start

Use the factory-memory-cache skill to automatically cache and retrieve frequently accessed project data like feature states, build commands, and execution plans to speed up agent command execution.

Frequently Asked Questions about factory-memory-cache

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

FAQPage Schema
How does memory caching speed up agent workflows for build automation?

Memory caching accelerates build automation by eliminating redundant file I/O overhead when agents repeatedly access the same project artifacts across sequential commands. It stores feature states and execution plans in a unified repo cache for cross-command reuse.

How do I cache feature states and execution plans for sequential agent commands?

To cache feature states and execution plans, leverage the `/memories/repo/` system to store frequently accessed data like build commands and codebase inventories. This enables cross-command reuse so sequential operations retrieve cached data instead of re-parsing files.

Does write-through caching guarantee data consistency for codebase inventories?

Write-through caching guarantees data consistency for codebase inventories by implementing source hash validation to ensure cached data never goes stale. It also features graceful degradation, falling back to direct file reads if the cache is unavailable or corrupted.

Can I use memory caching for large project build preparation in Myrmion AI Factory?

You can use memory caching for large project build preparation in Myrmion AI Factory to cut preparation time significantly. When running multiple IMPLEMENT --build commands, the cache eliminates repeated parsing of the codebase inventory and governance snapshot.

What are the cache size limits and limitations of unified repo caching?

Unified repo caching enforces a 500-line cache size limit to ensure data consistency and non-blocking command execution. When the cache fails or becomes corrupted, the system gracefully degrades by falling back to direct file reads.