skills.rest
shakhovskiya-create
shakhovskiya-createCOMMUNITY
Explore all skills by this author →
GitHub

cache-investigation

Persist one-shot investigations to a durable cache under docs/cache/<topic>.

Updated May 5, 2026
Search Tags:#workflow#architecture#documentation#dependencies#cache#investigations
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill cache-investigation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cache-investigation
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/solo-sdlc/skills/cache-investigation
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill cache-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist one-shot investigations (architecture survey, dependency map, library research) to docs/cache/<topic>/ so they're not re-done each session. Use BEFORE running any deep investigation skill (data-source-research, system-architect surveys). Reuse if cache fresh; otherwise refresh.

Core Features & Use Cases

  • Persist investigations to a topic-specific cache path under docs/cache.
  • Reuse cached results across sessions to save time during architecture, dependency, and library research tasks.
  • Automatically invalidate or refresh caches when underlying sources change or TTL expires.

Quick Start

Run cache-investigation for a topic before starting a deep-dive to create and refresh the cache under docs/cache/<topic>.

Frequently Asked Questions about cache-investigation

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

FAQPage Schema
How do I cache investigation results to avoid redoing architecture surveys every session?▼

Persist one-shot investigations to a durable cache under docs/cache/<topic> to avoid re-doing work in future sessions. The cache stores topic metadata and consulted sources for quick reuse.

What's the best way to reuse dependency map research across multiple workflow sessions?▼

Reusing dependency map research across sessions is done by persisting results to a topic-specific cache path under docs/cache. Cached results are reused if fresh, or refreshed when underlying sources change or TTL expires.

When do I need to refresh cached architecture documentation?▼

Refresh cached architecture documentation when the time-to-live expires or when underlying sources consulted during the investigation change. This ensures the persisted cache remains accurate for future sessions.

Can I use cache-investigation before running deep system-architect surveys?▼

Yes, apply cache-investigation before running deep investigation skills like data-source-research or system-architect surveys. It creates and refreshes the cache under docs/cache/<topic> to reuse fresh results.

Does caching one-shot investigations require any external dependencies?▼

Caching one-shot investigations requires no external dependencies. It operates by writing topic metadata and consulted sources directly to a durable path under the docs/cache directory structure.

Related Skills

Explore More Software Engineering Skills→
haizhouyuanhaizhouyuan

topic-research

Initialize topic research archives with templates, tasks, and mem0 insights.

Community
Advanced
danielcopperdanielcopper
3

zoom-out

Map module dependencies and architectural context for complex codebases.

Community
Basic
hotaqhotaq

doctor

Diagnose and repair Codex installation issues across plugin caches and configuration files.

Community
Advanced
marcusgollmarcusgoll
91

caching-strategy

Cache file reads, searches, network requests, and computed values across workflow phases with automatic invalidation by TTL and file modification.

Community
Advanced