work-status

Files (1)

• SKILL.md

SKILL.md (first lines)

# work-status

Read the [working agreement](../../references/workflow.md) unless it is already in this task's context. Stay read-only. Summarize documented progress; explaining a finding's reasoning uses [explain-work](../explain-work/SKILL.md), and judging current work requires a commissioned Review. From the available plan, assignments, and reports, explain what is complete and what remains uncertain. Identify the supporting documents and working state. When the plan records an isolated branch or worktree, name that checkout and whether reconcile is still open. Do not manufacture status from an identifier or treat absent reports as completion. Distinguish a completed phase from an achieved goal. If work remains, give the next useful action, who takes it, and why; ask for missing context precisely. Follow the documented phase outcome without starting another phase. If the goal is established as achieved, state that no further Workflow step is required.

For Auto-Work, name mode, phase, selected agents/settings and invocation gaps, spent/remaining rounds, latest independent Review, pending acceptance/delivery evidence, and next actor where relevant. Checks, acceptance and delivery are distinct outcomes. Status does not reset selections or budget, cancel work, switch mode or imply completion.

From geldmacher/workflow, MIT.

More from geldmacher/workflow