ulw-plan

A codebase planning agent addresses ambiguous scopes by reading the repository, conducting targeted research, and drafting a durable plan with explicit approval gating. This ensures all architectural decisions are finalized before any execution begins.

The best way to plan multi-module architecture changes without follow-up meetings is to generate a single decision-complete work plan. By anchoring decisions in codebase research and writing durable drafts, downstream workers can execute tasks independently.

To generate a planning document draft for a complex workflow, run the scaffold script for your specific slug. This creates a plan draft and skeleton under the .omo directory, ready for targeted research and explicit user approval.

Yes, the planning agent requires explicit approval before modifying the codebase. It enforces durable drafts and plans, ensuring that no execution begins until the user has reviewed and explicitly approved the generated work plan.

Yes, you can use this planning agent for large scope documentation tasks. It converts ambiguous scopes into a single plan by reading references and best practices, enabling downstream workers to execute the documentation with zero further interviews.

You should not use an automated planning agent for workflow automation when a task requires immediate execution without approval gating, or when the codebase scope is too small to justify durable drafts and targeted research overhead.