| name | task-delivery-sprint-loop |
| description | Run a /tasks-first implementation loop from active task selection through validation evidence and task status/comment updates. |
| argument-hint | Task ID/key, change slice, and validation scope |
| user-invocable | true |
| disable-model-invocation | false |
Task Delivery Sprint Loop
Inherits from task-core-loop.
Added Context
Use this when delivery should be anchored to /tasks records, not ad hoc notes.
Use MCP task tools first (task_get, task_set_status, task_add_comment) and use scripts to generate structured evidence payloads instead of writing long comments by hand.
Additional Inputs
- Task id or key.
- Target status transition (for example: Ready -> InProgress -> Done).
- Validation evidence required before completion.
Additional Procedure
- Load task context and linked pages before edits via MCP task tools.
- Move task status to
InProgress when implementation starts via MCP status tool.
- Apply core steps from
task-core-loop.
- Generate task comment evidence payload using:
pwsh ./Scripts/SkillHooks/New-TaskEvidenceComment.ps1 -TaskId <id> -Summary <summary> ...
- Submit the generated payload through MCP task comment tool.
- Transition task status only after validation evidence is captured.
Done Criteria
- Task record reflects current status accurately.
- Evidence is attached in task comments.
- Code and wiki notes are synchronized with the delivered slice.
