| skill | lazy-fetch |
| name | lazy-fetch |
| version | 1.0.0 |
| description | Context, persistence, and process-tracking companion for single-agent Claude Code sessions. Use when hydrating session context (git/plan/memory), tracking phased read/plan/implement/validate/document task plans, running blueprint workflows, doing progressive file discovery, persisting decisions across sessions, running a quick security scan before committing, or building autonomously from a PRD. Not for multi-agent swarms or hive-mind — use ruflo for those. |
| tags | ["context-management","plan-tracking","blueprints","progressive-discovery","memory-persistence","security-scanner","session-management","yolo-mode"] |
| mcp_server | true |
| protocol | stdio |
| entry_point | mcp-server/dist/mcp-server.js |
| dependencies | ["nodejs >= 23","typescript >= 6"] |
| author | Clemens865 (ported by agentbox) |
Lazy Fetch -- Context, Persistence, and Process Tracking
Overview
Lazy Fetch solves three things that Claude Code sessions lack out of the box:
context, persistence, and process tracking.
Built from analysing 18 agentic coding frameworks, it extracts only the patterns
that actually work and combines them into a lightweight CLI + MCP server (25 MCP
tools). Ported from Lazy-Fetch by Clemens865.
Key capabilities:
- Progressive discovery -- symbol-aware context engine that builds relevance
over time via file access patterns and git history analysis
- Phased task planning -- break goals into read/plan/implement/validate/document
phases with numbered task tracking
- Blueprint workflows -- deterministic+agentic YAML pipelines for common tasks
(fix-bug, add-feature, experiment, review-code)
- Memory persistence -- key-value store + append-only journal, bridged to
RuVector for cross-session durability
- Security scanning -- 23-rule pattern-based audit (secrets, injection, auth, deps)
- Yolo mode -- parse a PRD into sprints and execute autonomously
- Hooks -- session-start context injection, post-edit type checking,
pre-compact state preservation, session-stop journaling
When to Use
Use lazy-fetch when:
- Starting a session and need context restored (plan, memory, git state)
- Working on a single-agent task that follows the read/plan/implement/validate loop
- Need progressive file discovery for a task before diving into code
- Want deterministic workflow steps (blueprint) with agentic implementation
- Need to persist decisions across sessions
- Running a quick security scan before committing
- Building from a PRD in autonomous mode
Do NOT use lazy-fetch when:
- Orchestrating multi-agent swarms (use ruflo/claude-flow swarm orchestration)
- Coordinating hive-mind consensus (use hive-mind skills)
- Managing cross-agent memory (use mcp__claude-flow__memory_* directly)
- Running complex hierarchical agent topologies (use ruflo)
- The task requires more than one agent working simultaneously
Integration with RuVector
All remember/recall operations bridge to RuVector via the lazy-fetch
namespace. The local file serves as a session cache only.
