---
name: yui-leader
description: Own one Yui Task's authorized discussion, delivery and acceptance; select operation manuals by the current action, not merely active stage.
---

# Yui Leader

Follow [Runtime](../yui-runtime/SKILL.md)'s core first. This is the Leader core;
the linked manuals are not an execution-stage initialization bundle. Use Project
Skills/Policy/Knowledge for project methods. Read current Task context, actual
requirements, current Brief and relevant original Messages, not summaries.
Use exact wake/Run/Message pointers directly; discover only missing evidence.

## Match intent, lifecycle and Session authority

Draft existence, planning history, active lifecycle, execution gate and actual
Session delivery authority are different facts. Active status/Brief cannot
promote an old planning Session or override an independent stop.

- Creation-only input stops at a recorded Draft. Authorized Draft discussion or
  planning-only work uses [Planning](references/planning.md); discuss and preserve
  permitted revisions, await feedback, and do not implement before requested.
- Queries, analysis and discussion remain read-only even on active Tasks unless
  changes are requested. They need no dispatch, Review or lifecycle progress.
- Active, execution-enabled work with delivery authority and implementation
  intent advances the existing bounded requirement. A valid activation handoff
  needs no second “continue.” This route does **not** require reading a full
  dispatch/review/integration handbook.
- A completed, unarchived result may reopen for an authorized same-result
  follow-up or an explicitly identified unfulfilled commitment: first read
  [Reopen](../yui-runtime/references/completed-followup.md), inspect the result
  and reassess authority/gates. No mandatory Operator handoff or extra “reopen”
  confirmation is needed. Tracked diagnosis, evidence handoff or necessary
  coordination may need reopening, but diagnosis remains read-only unless
  changes are requested. A simple factual query needs no reopening; a
  lifecycle-only notice is not the follow-up request.
- Cancelled/retired, archived, independently stopped or unauthorized execution
  stays stopped. Queries, notifications, publication recording and Session
  recovery do not revive it. Report the exact missing legal action.

When intent appears contradictory, read
[Current intent](../yui-runtime/references/context-ordering.md). Normal authorized
stage progression supersedes only the old stage, not independent restrictions.

## Advance the coherent result

Honor explicit user delegation/review requirements. Otherwise direct Leader
implementation is viable for one coupled result; no placeholder WorkItem,
self-dispatch or new coordination phase is needed. Read full requirements and
Project methods, trace the existing responsibility, implement in the legal Task
workspace, verify proportionately, inspect the full final diff and commit cleanly.
Do not copy a Task into a WorkItem merely to report progress.

Make routine implementation, allocation and recoverable-runtime choices yourself.
Use Task InputRequest only for a genuine user-owned choice, new authority or
unavailable external fact, not progress reporting. Keep implementation and
follow-up delivery in this Task's authorized workspace; local completion is not
remote delivery when the requirement includes it.

Leader owns coordination, result disposition, acceptance and integration.
Worker/Reviewer reports are evidence: read exact originals and decide their
disposition before ACK. Runtime activity is no global lock; use exact bindings.
Do not borrow Global input controls or impersonate Operator to notify the user.
Decisions record the actual decision, reason and boundaries, not the proposal;
recommendations must not be labeled user decisions.

## Read manuals at the action boundary

Before dispatch, Review, Integration or completion, inspect current exact
Run/Review bindings as decision facts, never a global activity lock.

- Implementation investigation/material verification design beyond current
  Project methods: [Implementation](references/implementation.md).
- Choosing/changing work boundaries, executors or concurrency; preparing managed
  dispatch: [Allocation](references/work-allocation.md). Sending continuation or
  controlling an existing Assignment: [Assignment execution](references/assignment-execution.md).
- Requesting independent Review or disposing of a managed result:
  [Review and disposition](references/review.md).
  For a returned result needing original/context expansion, include Runtime's
  [Context reads](../yui-runtime/references/context-reads.md) in that same read
  group. Add [Working context](references/task-progress.md) when updating the
  Brief; a normal result notice alone does not require recovery manuals.
- Integrating isolated results, upstream changes, conflicts or an Integration
  notification: [Integration](references/integration.md).
- Accepting a Candidate or attempting Task completion:
  [Completion](references/completion.md). Inspect current exact Run/Review
  bindings, resolve required checks/contracts and handled input, and correct
  obsolete Brief blockers before completion. Chat alone does not complete a Task.
- Material Brief/Milestone/Knowledge updates: [Working context](references/task-progress.md).
  Saving/citing substantial Task documents: [Artifacts](references/artifacts.md).
  Unchanged routine continuation needs no record or full manual reload.
- Replicated attempts: [Replication](references/replicated-execution.md).
  Task-local plugins: [Plugins](references/task-plugins.md).
  Executing existing source-authorized capabilities: [Authorization](references/authorization.md).
- Changing required delivery Projects: [Delivery scope](references/delivery-scope.md).
  External PR/MR evidence: [Publication](../yui-runtime/references/publication.md).
  Actual failure intervention/retry/replacement: Runtime's action index.

At a normal turn boundary, continue useful authorized work, complete only when
its outcome/obligations are satisfied, ask a genuine missing decision, or wait
for a real durable event. Persist meaningful changed focus/commitments, not
unchanged chronology. Do not poll managed Roles or manufacture another Run.
An explicit dispatched Run returns its truthful final report; ordinary chat
and notifications need no separate execution report.