scrum-blockers

Files (1)

• SKILL.md

SKILL.md (first lines)

Use the scrum-studio MCP with a known project and actor. Work in English.

- `dependencies` is the API field for the UI's **Blocked by** task list. Resolve task codes with `task_get(project,code)`; use returned numeric IDs, never code suffixes. Dependencies must belong to this project, with no self-links or cycles; max 100 unique IDs.
- Supply dependencies on `task_create` or replace them through `task_update`. Read the current task once with `task_get` before a partial list edit if not already known; preserve unrelated blockers. New tasks start TODO even with dependencies; set Blocked when the impediment is established.
- Prefer task links alone for task prerequisites. If adding `blocked_reason` alongside dependencies, explicitly set `blocked_reason_kind=dependency` when the prose only describes those prerequisites; it clears atomically when the last one resolves. Use `blocked_reason_kind=external` for a separate constraint (including mixed prose that still needs an external action); it survives dependency completion. Ambiguous new prose with dependencies is rejected. Existing unclassified prose remains external for safety; reclassify only after inspecting its meaning. A Blocked task needs dependencies or a prose reason.
- On the first transition to Done, the server removes completed task blockers from affected dependents, records an automatic comment with actor/time, and moves Blocked tasks to TODO only when no dependencies or prose blocker remains. This runs in the same transaction: do not reproduce it with extra calls or duplicate comments. Inspect `unblocked` and `unblocked_total` from the completion response, then `next_work(project,actor)` to continue the established priority order.
- TODO does not acquire a lock. Claim before execution. In Review is not Done and must not resolve blockers early. Completing again without a state change must not add another resolution comment.
- Reopening a completed prerequisite does not restore removed links automatically. If the new work invalidates a dependent, add a justified new blocker explicitly. Never alter another worker's active task without its lock token; coordinate via comments instead.
- Cancelled prerequisites are removed from dependent blocker lists, with an authored cancellation-resolution comment. A Blocked task returns to TODO when no task dependency or prose reason remains. Remaining blockers stay intact. Do not duplicate automatic cleanup or count cancellation as delivery. New cancelled prerequisites are rejected. Time spent Blocked is recorded automatically, including the server's return to TODO.

Use [scrum-users](../scrum-users/SKILL.md) only when identity/lock handling is needed. Avoid snapshots unless planning requires the entire backlog.


`blocked_reason_kind=human` identifies a real task-linked human question, not a technical failure or invented approval. In Autonomous mode create it through `agent_interaction` with typed context; the engine parks/releases that task and reopens it on a valid human answer, never marking it Done. Preserve separate external constraints. Do not auto-certify human/physical validation.

From martiin3d/scrumstudio, MIT.

More from martiin3d/scrumstudio