Resolve blockers for blocked stories with human approval and journal documentation.
npx skills add https://github.com/Roeia1/SAGA --skill resolve-blocker
Please help me install this Agent Skill. Skill: resolve-blocker Source: https://github.com/Roeia1/SAGA/tree/main/plugin/skills/resolve-blocker Command: npx skills add https://github.com/Roeia1/SAGA --skill resolve-blocker
This skill helps engineering teams unblock blocked stories by diagnosing the blocker, coordinating a resolution with human approval, and documenting decisions in the story journal.
Invoke /resolve-blocker with a Story ID to begin resolving a blocker.
High-intent search queries and answers about installing and using this skill.
To resolve a blocker, invoke the resolve-blocker prompt with a Story ID. The skill reads story context and journal entries, proposes resolution options with implementation guidance, and requires explicit human approval before recording the resolution.
When multiple stories match, the skill disambiguates blockers by prompting you to select the correct story. It then locates and reads the relevant story and journal context to surface the specific blocker details before proposing resolutions.
Resolution decisions are documented by recording approved resolutions directly into the story journal. This maintains traceability and resumes work by ensuring the blocker diagnosis and chosen implementation guidance are persisted.
Yes, you need access to worktrees and story or journal files. The skill requires these to read story context, surface blocker details, and record approved resolutions back into the journal within the SAGA workflow.
No, explicit human approval is enforced before recording any resolution. The skill guides users through choosing a resolution with implementation guidance and rationale, but a human must approve the action before it is documented.
Implementation guidance includes multiple proposed resolution options with rationale. The skill analyzes story context and journal entries to offer specific, actionable steps for unblocking the story and resuming progress.
dohernandezCreate per-ticket git worktrees and set up development environments.
anis-marrouchiUpdate GitHub or GitLab issues to reflect Ralf story state changes.
mahg-esTrack blockers with SLA-based escalation and status updates.
hilaryosborneGuide engineering managers through root cause analysis and action planning.
