How do I install the Ultra Work Scout skill?

Run npx skillmds@latest add escoffier-labs/ultra-work-scout in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ultra Work Scout safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ultra Work Scout?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ultra Work Scout free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ultra Work Scout?

escoffier-labs (@escoffier-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ultra Work Scout by escoffier-labs — Agent Skill

Name: Ultra Work Scout
Author: escoffier-labs

Ultra Work Scout

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.

File contents

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.

---name: ultra-work-scoutdescription: 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-scoutUse 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".## MissionTurn 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 SetStart 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 Loop1. State the immediate local task you will keep yourself.2. Assign scouts concrete questions with disjoint read or write scopes.3. Keep moving on non-overlapping work while scouts run.4. Integrate only findings you can verify in the current tree.5. Run verification through Brigade:```bashbrigade work verify run --target . --command "<test command>" --capture ultra-work-scout```If `--capture` is not available in the installed Brigade version, run:```bashbrigade 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 ContractFinish with:- Scout questions asked and what changed because of them.- Files changed.- Verification command and result.- Any release blocker or follow-up that remains.

Frequently asked questions