{"id":83941,"plugin_id":"plugin_asdk_app_6a03edda077081918b92a9349232020d","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-06T06:35:22.117Z","digest":"dba6955306e9f19eee4c86302c016104015c6eaed2cfd0bbb91432cec99e5426","against":null,"payload":{"description":"Run a weekly review of AB Projects (ActionBridge) work — what got done, what slipped, what's blocked, and a proposed plan for next week. Use when the user asks for a weekly review or retro, wants to know what slipped or is overdue or blocked across projects, or asks to plan next week.","included_files":[],"name":"ab-weekly-review","skill_md_contents":"---\r\nname: ab-weekly-review\r\ndescription: Run a weekly review of AB Projects (ActionBridge) work — what got done, what slipped, what's blocked, and a proposed plan for next week. Use when the user asks for a weekly review or retro, wants to know what slipped or is overdue or blocked across projects, or asks to plan next week.\r\n---\r\n\r\n# Weekly review from AB Projects\r\n\r\nA retro plus a forward plan, grounded in the actual task data. Read everything before judging anything.\r\n\r\n## Gather\r\n\r\n1. `ab_get_my_projects` — the projects in scope (note overall progress percentages).\r\n2. `ab_get_schedule` — overdue / due-today / this-week across projects.\r\n3. `ab_get_my_tasks` — the full active list; anything with due dates in the past week that's still open counts as slipped.\r\n4. For each apparent blocker or long-stalled task (pick the few that matter), `ab_get_task` — check `Blocked: yes`, predecessors, and the latest comments so you can say *why* it's stuck, not just that it is.\r\n\r\n## Compose\r\n\r\n```\r\n**Weekly review — week of {date}**\r\n\r\nDone this week: {completed/moved items, celebrate briefly}\r\nSlipped: {tasks whose due date passed while open — [taskId] title, new-reality note}\r\nBlocked: {each with the blocking task or reason, from real dependency data}\r\nNext week: {proposed top 3-5, ordered — due dates first, then unblocking moves, then priorities}\r\n```\r\n\r\n- Be honest, not cheerful: if most items slipped, the review should say so and look for the pattern (one overloaded person? one stuck dependency chain?).\r\n- When one task blocks several others, lead with it — unblocking it is the highest-leverage move of next week.\r\n\r\n## Turning the plan into changes\r\n\r\nOnly on the user's confirmation, apply the plan with ab-project-manager conventions: `ab_update_task` with realistic new `due_date`s and a `note` like \"Rescheduled in weekly review\", `ab_complete_task` for anything actually finished but never closed. Never silently rewrite dates during the review itself.\r\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}