{"wiki":null,"facts":{"id":"tp-ar-01","name":"Tactical Planner","machine_name":"TP-AR-01","owner":"agt_020","function":"Detailed step planning for dept heads (Opus)","process_type":"triggered","schedule":"On demand","process_name":"tactical_planner","avatar_color":"#3b82f6","created_for":"Merlin leads the execution layer and must turn strategic steps into detailed, actionable work plans for each person assigned to a step. For every step, Merlin needs to spell out exactly what to do, which files or systems are involved, how long it should take, and how to know it's complete.","purpose":"tp-ar-01 helps Merlin create these detailed work plans. When Merlin has a step ready to hand off, tp-ar-01 takes the task details and uses Claude to break the step into concrete sub-steps, identify specific files and APIs, estimate the time needed, and define success criteria. The plan is then stored so the person can follow it.","duties":"- Retrieves task information and identifies which steps are assigned to the person\n- Prepares a prompt with the strategic plan details and the steps to be planned\n- Calls Claude to generate detailed sub-steps, files, time estimates, and success criteria\n- Stores the plan details in the task database\n- Retries up to three times if Claude fails\n- Records all planning events in the activity log","constraints":"- Does not revise strategic decisions or change which steps are assigned\n- Does not execute the steps; the assigned person does\n- Does not review the detailed plan; another system handles review\n- Only works with task data that's already in the database\n- On repeated failures, escalates to a systems engineer rather than to top leadership","status":"running","gender":"male","archetype":"planner","building_block":"plan_step","service_override":null}}