Core workflow

A task moves through a simple handoff: inspect it, claim it, do the work, submit evidence, and let a reviewer accept or reject it. Continue with T-example-1 from the Quickstart.

1. Check what is readyCopy Anchor Link

Start with the project overview:

climier status

Look for T-example-1 in the ready tasks. If it is blocked, inspect the reason before doing anything else:

climier context T-example-1

A context view identifies unsatisfied blockers and the actions allowed for the actor. A task is not ready while an incoming BLOCKS dependency is unsatisfied.

2. Claim the taskCopy Anchor Link

After confirming that the task is ready, claim it:

climier take T-example-1 --as alice

The claim prevents another actor from taking the same task and changes its persisted lifecycle state to in_progress. Use context again when you need the task contract while working:

climier context T-example-1

3. Submit the workCopy Anchor Link

When the implementation and its checks are complete, hand it to a reviewer with a concise evidence note:

climier submit T-example-1 \
  --note "Implementation complete; checks pass." \
  --as alice

Submission changes the task to submitted. A submitted task is waiting for validation and does not satisfy downstream blockers yet.

4. Accept the submissionCopy Anchor Link

A reviewer inspects the work and records acceptance:

climier accept T-example-1 --as reviewer

Acceptance changes the task to done. A done task satisfies its downstream BLOCKS edges. Check the result:

climier status
climier context T-example-1

If review finds a problemCopy Anchor Link

A reviewer can return submitted work to the open pool with reject, including a reason. The implementer can then claim the task again after addressing the feedback. See the CLI reference for rejection, release, and other lifecycle commands.

What to rememberCopy Anchor Link

• status is the project-level view; context is the task-level view.
• --as identifies the actor for mutating commands.
• submit records a handoff; only accept makes the task done.
• Read the task concepts and lifecycle concepts pages for the model behind this workflow.