Chief-of-staff Bot: summarize work through a task ledger
Use one intake and a ledger of owners, states and artifacts; propose a missing role before expanding the roster.
The source describes multiple Bots, daily summaries and research. This role card makes the coordinator’s ledger explicit without adopting a fixed roster or schedule.
Scenario and input
Section titled “Scenario and input”Synthetic tasks: T1 claims completion without an artifact, T2 awaits review, and T3 has no owner.
1. Standardize intake
Section titled “1. Standardize intake”Record outcome, sources, deadline and permitted actions, with centralized clarification of missing fields.
2. Create the ledger
Section titled “2. Create the ledger”Assign stable identities, one current owner, state and artifact path; a chat claim does not replace evidence.
3. Summarize from artifacts
Section titled “3. Summarize from artifacts”Attach artifacts and acceptance evidence to completed work and actionable explanations to pending or blocked work.
4. Control expansion and external actions
Section titled “4. Control expansion and external actions”Propose a role or handoff for unowned work before creating Bots or performing external actions.
5. Produce the concise brief
Section titled “5. Produce the concise brief”Report completed, review, blocked and next actions without repeated unchanged updates; confirm timing before scheduling.
A synthetic acceptance fixture
Section titled “A synthetic acceptance fixture”tasks.csv: task_id, owner, status, source, artifact, next_action. T1 needs verification, T2 needs review, and T3 needs assignment.
Copyable task brief
Section titled “Copyable task brief”Use the synthetic fixture to prepare the deliverable for Chief-of-staff Bot: summarize work through a task ledger. Do not connect real services yet.Input: Synthetic tasks: T1 claims completion without an artifact, T2 awaits review, and T3 has no owner.Requirements:1. Record outcome, sources, deadline and permitted actions, with centralized clarification of missing fields.2. Assign stable identities, one current owner, state and artifact path; a chat claim does not replace evidence.3. Attach artifacts and acceptance evidence to completed work and actionable explanations to pending or blocked work.4. Propose a role or handoff for unowned work before creating Bots or performing external actions.5. Report completed, review, blocked and next actions without repeated unchanged updates; confirm timing before scheduling.Return itemized records, evidence locations, unknowns and next steps, marking unperformed actions explicitly.Do not install tools, change access, purchase, publish, create Bots or schedule work in this pass.Acceptance and review
Section titled “Acceptance and review”Completed work has evidence, approvals are not reported as publication, and the roster has not expanded automatically.
Review the artifacts without taking external actions.Acceptance: Completed work has evidence, approvals are not reported as publication, and the roster has not expanded automatically.Separate pass, fail, untested and evidence; distinguish synthetic fixtures from live results.Stop on missing sources, permissions or uncertain outcomes and list the required evidence.Propose one next step with a recovery plan and wait for confirmation.Sources and applicability
Section titled “Sources and applicability”Original article: @sitinme; published 2026-10-13.
Index-to-source mapping: strong content match.
The collector reports viewing 8 images; 0 videos remain unwatched. Images show multiple roles and a Feishu competitor brief, illustrating consolidated outputs without establishing current prices.
Prices, interfaces and menus change. Check unresolved conditions against the actual account and current official documentation.
This page is based on the sources below, last checked on . If the interface looks different, send feedback or edit the page.Send feedbackEdit this page
91 related external resources →Official sources and original authors’ posts, each with a note on what was checked.