Repo Planning

Routing a unified Top-N task list across multiple repositories involves consolidating tasks from Freely, Rocket, and SOS, then generating three ready-to-execute master prompts with built-in validation gates tied to the work ledger.

Master prompts with validation gates are implementation-ready outputs generated for each repository, ensuring that routed tasks are mapped to catalog objectives and include a verification loop before updating the work ledger.

Yes, multi-repo planning specifically unifies Top-N tasks from Freely, Rocket, and SOS to output exactly three ready-to-execute master prompts, enforcing an exact structure to avoid consolidating tasks across repositories.

Validation gates map routed tasks to at least one objective from the objectives catalog and attach an objective-linked verification loop, ending each prompt with a Ledger Update JSON array reflecting existing work ledger fields.

Automating multi-repo task routing is best handled by generating structured master prompts that output a Ledger Update JSON array, ensuring only existing work ledger fields are updated without creating new items.

Task routing outputs exactly three master prompts to enforce exact output structure, avoid consolidating tasks across Freely, Rocket, and SOS, and streamline downstream execution for each repository independently.