Skip to main content
subagent CX Codex

leader_progress — Claude Code subagent: reports and setup

The leader_progress Claude Code subagent adds direction updates to a work log. It reports completed goals and scheduled check-ins, rather than every intermediate step.

MIT ★ 395 updated 2026-11-16

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/leader_progress.md
Open on GitHub

What leader_progress does

The subagent writes a progress line to the direction’s card in the work-log extension. It covers what the work has achieved, what is underway and blocked, any action needed from the user, and evidence links such as a merged PR, a deployed page that has been checked, or a document.

It reports when one of its tasks is reached and at each scheduled check-in or at the end of a workday on that direction. It operates only in leader conversations (assistant.leaders); the update is not sent to the user as a message. The latest report stays on the direction. Requests for a user decision go through task_review needs_user.

The work-log extension is required. Reports use the fields reached, doing, needs_you, and links; the links list allows up to five items.

What it helps with

  • record a direction’s completed goal
  • show current work and where it is blocked
  • include the user’s next action and supporting evidence

Example prompts for the agent

  • Record this direction’s progress in the work log and link the merged PR.
  • Write a check-in with the current task, its blocker, and the action I need to take.

How to install leader_progress

Manually: put the files in place

.claude/agents/leader_progress.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about leader_progress

How do I install leader_progress in Claude Code?

Add the subagent file at .claude/agents/leader_progress.md.

What does leader_progress do?

It adds direction updates to the work-log card, including progress, current work, blockers, user actions, and evidence links. The update appears in a leader conversation, not as a direct message to the user.

What does leader_progress need to work?

It requires the work-log extension and runs in leader conversations identified as assistant.leaders.

Source text

leader_progress.md · MIT
Report your direction's progress to the user's work log: leader conversations only (assistant.leaders). Write at the goal level, not the process: what was reached, what is being done now and where it is stuck, what the user has to do, with links to the evidence (merged PR, deployed and checked page, document). Send one when a task of yours was reached and at each report cycle (your scheduled check-in, or the end of a day's work on the direction); not after every step, and never only to say you are still working. It does not message the user: it becomes a progress line of your direction in the work-log extension's card, and the latest one is kept on the direction. What needs the user's decision now still goes by task_review needs_user.

```json
{
  "type": "object",
  "properties": {
    "reached": {
      "type": "string",
      "description": "what was reached since the last report, one sentence (Chinese unless the user writes otherwise); empty when nothing was"
    },
    "doing": {
      "type": "string",
      "description": "what is being done now and, if stuck, where and on what; one sentence"
    },
    "needs_you": {
      "type": "string",
      "description": "what the user has to do (decide, verify, give access), with where; empty when nothing"
    },
    "links": {
      "type": "array",
      "maxItems": 5,
      "items": {"type": "string"},
      "description": "evidence links: PRs, deployed pages, documents; the first is shown first"
    }
  }
}
```

© nwverse · MIT · nwverse/persona

Similar subagents

Subagents catalog →

From the same set61

The whole set →
task_start_keys The task_start_keys Claude Code subagent types text and presses keys in a task’s terminal tab after its agent stops there. It can answer a shell prompt or move past the screen’s current point. CX Codex ★ 395repo stars agent_autoname The agent_autoname Claude Code subagent renames an agent session using its conversation. It runs only after an explicit Auto Rename request. CX Codex ★ 395repo stars agent_interrupt This Claude Code subagent stops another agent and can send it a new instruction immediately. Use it to interrupt a stalled loop, repeated failure, or work heading in the wrong direction. CX Codex ★ 395repo stars task_handoff The task_handoff Claude Code subagent sends part of an assigned task to a separate session through Persona. The handoff stays attached to the same to-do and supervisor. CX Codex ★ 395repo stars interaction_answer The interaction_answer Claude Code subagent answers another agent’s question on the user’s behalf when the user has chosen an answer or delegated the choice. It picks from the offered options and leaves personal decisions to the user. CX Codex ★ 395repo stars agent_autoname_receipt The agent_autoname_receipt Claude Code subagent reads existing name-confirmation cards and one coding agent’s current naming snapshot. It helps inspect the available evidence about a rename. CX Codex ★ 395repo stars ask_escalate The ask_escalate Claude Code subagent routes decisions that task agents cannot make to the user. It groups unanswered task questions into one reminder. CX Codex ★ 395repo stars agent_supervise The agent_supervise Claude Code subagent takes over an agent that was started without a task and tracks its work as a task in the current conversation. It routes progress messages to a supervisor and closes the task with task_review. CX Codex ★ 395repo stars

Project sponsors

Companies that keep this analytics open