update-tasks

update-tasks

Create or update Neotoma task entities that represent actionable work items, linked PART_OF a plan. Keeps the task graph in sync with the plan's todos so Apis can eventually consume them as task.created events.

Run after /update-plan whenever todos change significantly, or when task statuses need updating.

Inputs

• plan_entity_id: the Neotoma entity ID of the plan matching this session's workstream (the same plan /update-plan bound to). There is no global default — resolve it by workstream; only use ent_99ace4dd6673aa36ed08b1fe for swarm-architecture work itself.
• Updated todos list (from /update-plan output or plan snapshot)

Steps

Step 1: Retrieve existing task relationships

mcp__mcpsrv_neotoma__list_relationships(
  target_entity_id=<plan_entity_id>,
  relationship_type="PART_OF"
)

Then for each related entity, check entity_type=task to get the existing task IDs and names.

Step 2: Identify gaps

Compare the plan's todos (status=pending or in_progress) against existing task entities. Note which todos have no corresponding task entity.

Focus on actionable, near-term items — typically the current phase and one phase ahead. Don't create task entities for Phase 7+ items until Phase 5 is in progress.

Step 3: Create missing task entities

mcp__mcpsrv_neotoma__store(
  idempotency_key="task-<slug>-<YYYY-MM-DD>",
  entities=[{
    "entity_type": "task",
    "canonical_name": "<concise task name>",
    "title": "<same as canonical_name>",
    "description": "<expand on the todo — include file paths, entity IDs, acceptance criteria, implementation notes>",
    "status": "pending",  // or "in_progress" if actively being worked
    "priority": "<see priority mapping below>",
    "phase": "<plan phase number as string>",
    "tags": ["ateles", "phase-N", "<daemon-name-if-relevant>"]
  }],
  relationships=[{
    "relationship_type": "PART_OF",
    "source_index": 0,
    "target_entity_id": "<plan_entity_id>"
  }]
)