| name | memory-query-resume |
| version | 0.9.5 |
| description | Query curated project memory before answering repo-specific questions, and use resume to get back into flow after interruptions |
Memory Query And Resume Skill
Use this skill when:
- the user asks how this repository works
- the user asks to explain code, a file, a module, an architecture path, or the whole codebase
- the user asks a project-specific question that should be grounded in stored memory
- the user returns after an interruption and wants to get back into flow
- the user asks what changed since they were last here
Do not use this skill for:
- plan approval or execution-start transitions
- plan-completion verification
- post-task memory capture after work is done
Scripts
Query curated project memory:
go run ./.agents/skills/memory-layer/scripts/main.go query-memory "<question>"
Resume a project after an interruption:
go run ./.agents/skills/memory-layer/scripts/main.go resume-project [project-slug]
Workflow
- Query memory before answering project-specific questions.
- For interruption-recovery prompts, use
resume-project instead of a generic query.
- Use the returned evidence or resume pack in your answer.
- For code or codebase explanation requests, inspect the relevant code or docs before making claims.
- After answering an explanation request, use
memory-remember to store the distilled reusable explanation when it produced durable project understanding.
- Prefer insufficient evidence over unsupported conclusions.
- Never invent provenance.
Model Routing
Keep this skill on the stronger engineering path.
Runtime Requirement
This focused skill uses the shared Go helper under .agents/skills/memory-layer/scripts/.
go must be available on PATH for these helper commands to run.
