メニュー
Use when the user asks for ultra work, scout work, broad pre-implementation scouting, or parallel investigation before a large Brigade task. Designed for Codex and other SKILL.md harnesses that can delegate or split work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when asked to find bugs, hunt for correctness issues, sweep a codebase for defects, or verify a repo behaves as intended. Not for style or architecture review; this is defect-finding only.
Use when reviewing a diff or module for hidden assumptions - things the code takes for granted that nothing guarantees - or when asked "what could break this later", "what does this assume", or to harden code that works today. Complements bug-hunt: bug-hunt finds defects with triggers today; this finds the ones waiting for tomorrow.
Use when a diff carries side effects - database writes, migrations, file mutations, network calls, payments, queue messages - to check whether running it twice is safe. Also when reviewing retry logic, crash recovery, or anything a scheduler, queue, or impatient caller might re-run. Silent when the diff touches no side-effecting surface.
Use at the start of any work session and whenever you verify a change in a Brigade-wired repo or workspace - routes work through Brigade so verification, outcomes, evidence export, and handoffs are captured (verify with capture → outcome from run → evidence brief next time) instead of leaving Brigade installed-but-dormant. Triggers on starting a task, running tests/checks, or finishing a session.
Create an Obsidian-formatted markdown note documenting the current session topic. Use when the user says /note, 'save this to Obsidian', 'write a note about X', or asks to document a troubleshooting session, system concept, coding pattern, or workflow. Writes to ~/notes/<slug>.md and syncs to the configured Obsidian inbox. If an argument is provided after /note, use it as the topic; otherwise review the conversation.
Use when about to claim anything works, is fixed, is complete, or passes - before committing, replying to the user, or moving to the next task. Also use when relaying a subagent's or tool's success report, and especially at the end of a long session when the pull to say "done" is strongest.
| name | ultra-work-scout |
| description | Use when the user asks for ultra work, scout work, broad pre-implementation scouting, or parallel investigation before a large Brigade task. Designed for Codex and other SKILL.md harnesses that can delegate or split work. |
Use this skill when a task is important enough to scout before changing code, especially when the user asks for "ultra work", "scout this", "use scouts", "use subagents", or "really scope this out".
Turn a large request into a small number of parallel, bounded scouting jobs, then bring the results back into one implementation path. Scouts gather context and risks; they do not replace the main agent's ownership of the final change.
Start with the smallest set that can answer independent questions:
Only add more scouts when the work naturally splits into independent repos or subsystems.
brigade work verify run --target . --command "<test command>" --capture ultra-work-scout
If --capture is not available in the installed Brigade version, run:
brigade work verify run --target . --command "<test command>"
brigade outcome capture ultra-work-scout --run-id latest --kind skill
Finish with: