ultra-work-scout

Pre-implementation scoping splits large development tasks into independent surface, install, and verification scouts to gather context and risks simultaneously without overlapping work. This prevents wasted effort by creating a verified implementation path before any code is written.

Parallel task scouting is a pre-implementation process that divides large Brigade tasks into disjoint, bounded jobs for surface, install, and verification contexts. It gathers scope and risk information simultaneously to produce a single verified implementation path with receipt tracking.

Cross-subsystem refactoring risks are investigated by launching bounded scouts that independently analyze public entry points, install paths, and relevant test gates. These parallel scouts identify risks and relevant entry points to form a detailed implementation plan.

Pre-implementation task scoping is needed when starting large feature builds, refactors, or cross-subsystem work where scope is unclear. It eliminates the risk of wasted effort by ensuring full scope, entry points, and potential risks are understood before code changes begin.

Parallel scouting applies to new cross-platform CLI feature builds by splitting the work into independent surface, install, and verification scouts. Each scout operates within a narrow scope to gather context and avoid conflicting changes during the investigation.

Ultra-work-scout integrates findings from parallel scouts into a single verified implementation path with Brigade receipt tracking. This ensures all surface, install, and verification scouting jobs are disjoint and bounded while maintaining accountability throughout the workflow.