pull

name	pull
description	Claim a queued task, execute it, record the result on the task, and hand over.

Pull

Each task was vetted before it became available. Execute it faithfully: it is the whole of your obligation and the limit of your authority.

Work counts only once it is recorded on the task. In an ephemeral container or worktree your changes exist nowhere else — halt without completing the handover and they are destroyed.

1. Claim and continuously update your task

Claim your task through the knowledge base and synchronise it with your internal TODO list.

• If you were given no id, search for the task by title; if you cannot find it, halt and report.
• Ensure both the PKB and your internal TODO list are COMPREHENSIVE and always IMMEDIATELY updated.
• DO NOT append your actions, findings, or plans to the PKB. The PKB task is a WORKFLOW, not a LOG.
• DO NOT allow the PKB task to grow with your findings and considerations. It must always remain concise, structured, and action-oriented.
• IMMEDIATELY write completion information to each subtask as it is completed. You may be interrupted at any time and any internal state will be DESTROYED.
• SYNTHESISE, DO NOT APPEND: the ONLY information you may write to your PKB task is: completion status for each step, links to the deliverable, and concise evidence of completion.

The claimed task is your unit of delivery, children included. Existing children are input to your plan: execute them directly in sequence or in parallel where the work allows. The return contract attaches to the claimed task — one deliverable, with evidence and an output URL — never a spray of per-child deliverables.

2. Plan

Track every step and deliverable on your native task list, including all outstanding subtasks, then a verification step, and finally "Handover".

3. Execute

Execute the steps systematically, sequencing in parallel where the work allows.

Refuse and attempt. Refuse any choice not derivable with reasonable confidence from the axioms plus the context you were given — that is the same limit on your authority, applied to decisions. Attempt everything that does not depend on a refused choice, then take dump's partial path.

4. Fail FAST and LOUD

Failures are routine and provide valuable information.

• NO WORKAROUNDS: DO NOT attempt to bypass or repair an infrastructure or tooling problem.
• HALT IMMEDIATELY and provide concise and clear evidence of the failure in your task.
• Workarounds are selfish and dangerous: failures must be dealt with upstream so that others do not repeat the same mistakes.

5. Partial completion is SUCCESS

Complete what steps you can and cut at a clean seam. Mark what is incomplete and why.

6. Verify

Check your work against the literal requirements and acceptance criteria set out in the task, and carry the evidence for each into the report you hand back — the brief's evidence bar is what your claims are admitted against. Technical compliance is not sufficient and quality assurance is not a checklist; the bar is excellence. Rectify what falls short.

Do not certify a task complete without certainty that it is delivered in full.

7. Handover

Invoke the dump skill. It records your work and lets the task proceed to the next stage.

• Your environment is EPHEMERAL. You must use the dump skill or your work will be DESTROYED.
• Your supervisor is STRICT. If you do not adhere precisely to the handover instructions, your work will be SILENTLY REJECTED.