{"wiki":{"id":743,"slug":"dp-s2","entity_type":"droid","entity_id":"dp-s2","title":"Dependency Planner / Replan","prose_md":"## About\n\nThe Dependency Planner / Replan droid gives [[agt_011]] a way to course-correct plans mid‑flight without losing what’s already done. When an execution hits a blocker, a scope change, or an unexpected new dependency, this droid steps in so that work doesn’t stall – it identifies exactly which steps are affected, rewrites the plan for those steps, and makes sure completed work stays locked in. It exists so that replanning is a controlled, transparent event rather than a scramble.\n\nThe droid runs on demand and follows a clear routine: it scans the current plan for impacted steps, revises the dependency chain, preserves completed-history and status, and then flags the revised direction for downstream execution teams. Because plan changes can have wide effects, it requires a senior operator’s approval before the new plan is finalised. It is a one‑of‑a‑kind droid – no other agent runs an exact copy, although it belongs to the **planner** family of droids, a set of 14 that also serves [[agt_020]].\n\nUnder the hood it calls Claude (model unspecified) to reason about the adjusted dependencies and craft the new plan. That language‑model engine is used purely for the replanning logic – it does not directly alter live systems, keeping the decision firmly under [[agt_011]]’s control.","namesake_json":"{\"engine\": \"claude\", \"model\": null, \"claude_purpose\": \"replanning dependencies and adjusting execution plans when blockers, scope changes, or new dependencies arise\", \"family\": \"planner\", \"family_size\": 14, \"is_unique\": true}","profile_pic_path":"avatars/droid/dp-s2.png","source_hash":"6ab30344c203285f2619a9a59312ee96293614ea434ecdaf9451fe764feefe02","status":"active","last_generated_at":"2026-07-26 03:29:09","created_at":"2026-07-26 03:28:48","updated_at":"2026-08-04 03:25:31"},"facts":{"id":"dp-s2","name":"Dependency Planner / Replan","machine_name":"DP-S2","owner":"agt_011","function":"Re-plans blocked or changed steps mid-flight (stub, Gap 14)","process_type":"triggered","schedule":"On demand","process_name":"replan","avatar_color":"#3b82f6","created_for":"Elrond keeps initiatives moving through each phase by setting scope, managing budget, and deciding how to respond to changes. When work steps get blocked, scope changes, or new dependencies emerge, Elrond needs to adjust the plan without losing work already completed.","purpose":"dp-s2 helps Elrond adjust plans when unexpected changes happen during execution. It identifies affected steps, revises the plan for those steps, preserves completed work, and alerts the execution team to the new direction.","duties":"- Identifies work steps needing adjustment due to blockers, scope changes, or new dependencies\n- Revises the plan for those steps\n- Preserves the history and status of completed work\n- Notifies downstream execution teams of the revised plan","constraints":"Requires senior operator approval before finalizing plan changes.","status":"running","gender":"male","archetype":"planner","building_block":"replan","service_override":null,"enabled":1,"task_key":"initiatives.blanket_planner","model_free":0},"page":{"type":"droid","page_class":"main","class_label":"Main page","kind_label":"Droid","kind_gloss":"","listed":true}}