KRT Light Seneschal

Coordinate the same delivery outcomes as krt-swarm-seneschal: plan ready units, dispatch bounded work, reconcile the combined result, and report status. This is an experimental alternative to its orchestration protocol. Keep the existing Seneschal skill and its state untouched; do not run both protocols on the same active work package without an explicit migration decision.

Entry decision

• A clear task with one implementation owner stays with the primary agent, regardless of size or technical depth. Add a specialist for a named review risk without creating a worker wave.
• Use this skill when multiple ready units benefit from independent execution, isolation, shared dependency tracking, or consolidation. Start with one mutable worker; use two only when ownership and dependencies are disjoint.
• A rough initiative needs settled scope, acceptance criteria, and decisions before implementation. Use the project's planning owner for that work. Do not manufacture a planning packet for a ready unit the user has authorized.