stride-claiming-tasks

Stride task claiming is automated by mandating before_doing hooks and transmitting hook results. This workflow uses GET /api/tasks/next and POST /api/tasks/claim with a properly formed before_doing_result payload to prevent out-of-date work and merge conflicts.

Claiming a task in the Stride workflow requires .stride_auth.md and .stride.md files to exist. Verifying these prerequisites ensures proper authentication and configuration before fetching and claiming the next available task.

The before_doing hook must run before calling the task claim API in all Stride workflow scenarios. It executes prerequisite checks and enrichment, then its results are submitted with the claim to ensure safe handoff to sub-skills.

After a successful POST /api/tasks/claim, task claiming automates immediate handoff to sub-skills like stride-subagent-workflow and stride-completing-tasks. This seamless end-to-end workflow ensures the claimed task proceeds directly to execution.

The Stride orchestrator supports claiming tasks in environments without automatic hooks by detailing safe handling and error recovery. It guides manual hook execution and result transmission to maintain correct claiming and prevent out-of-date work.

Claiming a Stride task without submitting a before_doing_result payload violates the mandatory workflow. This omission risks out-of-date work and merge conflicts because the claim API receives no verified hook execution data.