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
.claude/agents/leader_progress.mdWhat 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.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/leader_progress.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/leader_progress.mdCursor also reads .claude/agents/
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