メニュー
Use when a graph already exists and the user needs retrieval, tracing, explanation, or gap detection from graph memory before reopening the full corpus.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | memory-query-workflow |
| description | Use when a graph already exists and the user needs retrieval, tracing, explanation, or gap detection from graph memory before reopening the full corpus. |
Use existing graph memory first.
Query the graph before rereading source files unless the graph is missing, stale, or too weak for the question.
apx check graphify
graphify-out/graph.json| Question shape | Action |
|---|---|
| broad question about connected concepts | graphify query |
| trace between two concepts, files, or systems | graphify path |
| explain one concept or node in context | graphify explain |
| no graph exists | switch to memory-build-workflow |
| graph exists but corpus changed | recommend graphify --update before trusting results |
graphify-out/graph.json exists.query, path, or explain based on question shape.query for a question that clearly needs a path traceUse when starting work in a repository with Agent Powerups installed, when a task may match a reusable local skill, command, workflow, hook recipe, AGENTS.md template, or MCP feature.
Use when validating rendered web pages, local dev servers, browser automation, screenshots, forms, auth sessions, or UI evidence with strict browser safety boundaries.
Use when designing or reviewing filesystem MCP access, path boundaries, allowed roots, method allowlists, and safe local file operations.
Use when implementing any feature or bugfix, before writing implementation code
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Use when receiving code review feedback, before implementing suggestions — requires technical verification and reasoned pushback, not performative agreement or blind implementation.