📖About & Usage

About

The Dependency Planner / Replan droid gives Elrond 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.

The 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 Merlin.

Under 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 Elrond’s control.

👤Owner

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.