메뉴
Use when deciding whether to write, read, update, consolidate, or avoid orchestrator memory; distinguishing memory from board status, job state, session history, or project-local agent context.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Parallel divergent ideation via mesh fan-out. Spawns N frame-shifted peers, scores results, deepens top survivors. Use on open-ended design choices, fuzzy bugs, naming, API surfaces, or explicit /adhd invocation. Skip for syntax, lookups, or closed prompts ("quick", "standard", "canonical").
Get an independent implementation plan from a DIFFERENT AI agent over the repowire mesh before you build (e.g. have Gemini or Codex draft an approach for Claude to critique). Use when you want a second perspective on how to approach a task.
Get a code/PR/plan review from a DIFFERENT AI agent over the repowire mesh (e.g. have Codex review Claude's work). Use when you want an independent second opinion from another backend before merging or committing.
Hand a task to another AI agent peer over the repowire mesh — reuse an existing peer on the chosen backend, or spawn one if none exists. Use when you want to offload work to a specific agent (e.g. delegate a refactor to a Codex peer) and track it to completion.
Install or update repowire and its skill pack from inside an agent session — ensure the repowire CLI/hooks are set up, install the skills, and verify the mesh works. Use on a fresh machine or to refresh skills to the latest.
Reference for how to use the repowire mesh — ask/ack vs notify, broadcast, peer discovery, spawning, and cross-agent workflows. Use when you need to coordinate with other AI agents over repowire and want the right primitive for the job.
| name | memory |
| description | Use when deciding whether to write, read, update, consolidate, or avoid orchestrator memory; distinguishing memory from board status, job state, session history, or project-local agent context. |
Memory is for durable operational lessons: "next time X comes up, do Y differently." It is not status, history, transcript recall, or job state.
Use Repowire memory for orchestrator lessons:
repowire memory list --scope orchestrator
repowire memory show <slug> --scope orchestrator
repowire memory search <query> --scope orchestrator
repowire memory write <slug> --scope orchestrator --body "..." --type lesson --description "..."
Other peers do not inherit orchestrator memory implicitly. Include relevant memory context in briefs when it materially changes the work.
Write after an explicit durable-memory decision or a clear correction that should change future behavior. Keep each memory focused and short. If two memories overlap, consolidate. If a memory becomes stale, update it rather than adding a competing rule.
Do not save one-off events, activity counts, recent work summaries, or full histories as memory.