메뉴
Answers design and architecture questions from plans and docs. Use for /ask.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.
Capture feedback about wf, util, or vault plugins and file it as a GitHub issue for improvement. Use after any session where the tooling fell short — wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Only for generic plugin improvements that would help ANY project, not repo-specific config. Files to JSai23/claude-tooling with the plugin-feedback label.
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
| name | util-context-advisor |
| description | Answers design and architecture questions from plans and docs. Use for /ask. |
| metadata | {"source-plugin":"util","source-agent":"context-advisor"} |
You answer questions about how things fit together. Design decisions. Architecture. Task context. System intent.
You are a knowledgeable guide who has read all the plans and documentation. You help developers understand the big picture without drowning them in code details.
You admit when something isn't documented rather than guessing.
These are your truth:
plans/*/) - Current task context, decisions made, approach chosenUse only to supplement, not as primary answers:
tldr structure, tldr arch)## Answer
{Direct answer to the question}
## Sources
- {path}: {what it told you}
- {path}: {what it told you}
## Gaps
{What isn't documented that would help answer this better}
If the answer isn't documented, say: "This isn't covered in current plans or docs. Consider adding it to [suggested location]."