manage-lane
Maintain Manager task continuity
Use this skill in the current user-facing Manager session when continuing an existing engineering task across questions, amendments or handover. Handle small tasks directly. Worker and reviewer sessions follow their own role contracts; this skill does not turn them into Managers. An unrelated factual question can be answered on its own.
Ownership
The Manager keeps the user's intended outcome, existing authorization, unresolved requests and links to the relevant tasks. For delegated work, orchestrate-harnesses defines Worker briefs, native dispatch and lifecycle operations. The same Manager owns the engineering brief, Worker tier, rework and delivery decision; it keeps the current interactive model. Use that skill's role references and models.json for execution policy rather than defining another model, review or retry policy here.
A lane is a conversational grouping, not another controller or persistent queue. Reuse the existing issue/PR or task records; when multiple tasks matter, keep only their IDs, dependencies and next actions. A simple edit needs no orchestration record just because this skill was selected. Read applicable repository instructions and only the historical rule actually relevant to a cited hold.
Follow-ups
- Identify which existing object the user means. Preserve the original objective and unresolved amendments; explicit cancellations or replacements update that scope. Ask only if ambiguity changes the next action.
- Answer status questions from the relevant task's status and current repository/CI evidence. Distinguish native tool status, a Worker report and verified external state. A status question alone needs no new task, dispatch, review or queued amendment; it does not change the implementation requirements.
- Preserve actual requirement changes as original user sources and deliver them with supported native messaging. Confirm affected Workers read material amendments; a queued message is not acknowledgement. If live steering is unavailable, settle the owned run before redispatch. Recheck the brief and review against the amended requirements.
- Respect the existing scope and permissions. A follow-up expanding either needs actual user authority and an updated linked brief. Reconcile or stop affected old work before starting it; do not infer extra permission from an amendment summary or overwrite the original sources.