Run any Skill in Manus with one click

ultra-work-scout

Stars61

Forks4

UpdatedJuly 9, 2026 at 09:45

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

escoffier-labs

escoffier-labs/brigade

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

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.

ultra-work-scout

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".

Mission

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.

Default Scout Set

Start with the smallest set that can answer independent questions:

Surface scout: find the public commands, docs, templates, and user-facing entry points that must change.
Install scout: trace init, upgrade, profile, and default-install paths so new users get the intended behavior.
Verification scout: identify focused tests, full checks, and existing flaky or environment-sensitive gates.

Only add more scouts when the work naturally splits into independent repos or subsystems.

Main Agent Loop

State the immediate local task you will keep yourself.
Assign scouts concrete questions with disjoint read or write scopes.
Keep moving on non-overlapping work while scouts run.
Integrate only findings you can verify in the current tree.
Run verification through Brigade:

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

Boundaries

Do not spawn scouts for tiny, single-file fixes.
Do not let scouts mutate the same files unless you explicitly split ownership.
Do not trust a scout's success claim without reading the diff or output that matters.
Do not skip the final Brigade verify and outcome capture.

Output Contract

Finish with:

Scout questions asked and what changed because of them.
Files changed.
Verification command and result.
Any release blocker or follow-up that remains.

More from this repository

same repository

bug-hunt

escoffier-labs/brigade

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.

2026-07-1261

latent-premises

escoffier-labs/brigade

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.

2026-07-1261

retry-safety

escoffier-labs/brigade

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.

2026-07-1261

brigade-work

escoffier-labs/brigade

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.

2026-07-0961

note

escoffier-labs/brigade

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.

2026-07-0961

check

escoffier-labs/brigade

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.

2026-07-0261

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.

ultra-work-scout

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".

Mission

Default Scout Set

Start with the smallest set that can answer independent questions:

Surface scout: find the public commands, docs, templates, and user-facing entry points that must change.
Install scout: trace init, upgrade, profile, and default-install paths so new users get the intended behavior.
Verification scout: identify focused tests, full checks, and existing flaky or environment-sensitive gates.

Only add more scouts when the work naturally splits into independent repos or subsystems.

Main Agent Loop

State the immediate local task you will keep yourself.
Assign scouts concrete questions with disjoint read or write scopes.
Keep moving on non-overlapping work while scouts run.
Integrate only findings you can verify in the current tree.
Run verification through Brigade:

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

Boundaries

Do not spawn scouts for tiny, single-file fixes.
Do not let scouts mutate the same files unless you explicitly split ownership.
Do not trust a scout's success claim without reading the diff or output that matters.
Do not skip the final Brigade verify and outcome capture.

Output Contract

Finish with:

Scout questions asked and what changed because of them.
Files changed.
Verification command and result.
Any release blocker or follow-up that remains.