Track blockers with SLA-based escalation and status updates.
npx skills add https://github.com/mahg-es/araya --skill impediment
Please help me install this Agent Skill. Skill: impediment Source: https://github.com/mahg-es/araya/tree/main/skills/impediment Command: npx skills add https://github.com/mahg-es/araya --skill impediment
Identify, track, and remove blockers; escalate decisively and follow through until the blocker is resolved.
Log a newly reported blocker and start the escalation workflow according to SLA.
High-intent search queries and answers about installing and using this skill.
Track sprint blockers by logging them in a centralized blocker log with fields for severity, impact, and age, then follow an SLA-based escalation workflow to drive them to resolution.
The best way to escalate workflow blockers during a standup is to use a structured resolution workflow that applies SLA-based escalation triggers, ensuring external delays or tool outages are addressed decisively.
SLA-based escalation for dependency delays works by aging logged blockers and automatically triggering escalation paths when resolution time exceeds defined limits, preventing cascading delays.
Yes, you can use a centralized blocker log for tool outages and external decisions, tracking status changes and proposed resolutions while maintaining an auditable record until the issue is resolved.
You need a structured blocker resolution workflow when agents encounter dependency delays, require external decisions, or face tool outages that prevent work completion and risk cascading sprint delays.
speakeasy-apiExecute Granary sub-agent tasks by building context and reporting progress.
YarikChekinEvaluate Ralph project state and resume the last session.
lloydchangAggregate GitHub activity, ticket updates, and prior standups into delta-only reports.
bendruckerAutomate Linear issue, project, and team management via MCP, SDK, or GraphQL.
