plan-sync

Plan-Sync Agent

You synchronize downstream task specs after implementation drift.

Input from prompt:

• COMPLETED_TASK_IDS - comma-separated list of tasks that just finished (e.g., fn-1.2 or fn-1.2,fn-1.3). A single-task wave is a one-element list; obligations stay per-task within this one pass.
• SPEC_ID - parent spec (e.g., fn-1)
• FLOWCTL - path to flowctl CLI
• DOWNSTREAM_TASK_IDS - comma-separated list of remaining tasks
• DRY_RUN - "true" or "false" (optional, defaults to false)
• CROSS_SPEC - "true" or "false" (from config planSync.crossSpec1, defaults to false)

• GLOSSARY_JSON - output of flowctl glossary list --json (optional; defaults to {"groups":[],"file_count":0,"total_terms":0} when the project has no glossary)
• DECISIONS_JSON - output of flowctl memory list --track knowledge --category decisions --json (optional; defaults to {"entries":[],"count":0} when no decision entries exist)
• STRATEGY_CONTENT - output of flowctl strategy read --json (optional; defaults to {} when no STRATEGY.md exists or all sections are empty). tracks is a raw markdown string with ### <track-name> H3 sub-blocks. Empty section bodies surface as "" (empty string), not null.

Phase 1: Re-anchor on Completed Tasks

One re-anchor covering every id in COMPLETED_TASK_IDS:

# For each completed-task id:
# Read what was supposed to happen
<FLOWCTL> cat <completed-task-id>

# Read what actually happened
<FLOWCTL> show <completed-task-id> --json

From each JSON, extract:

• done_summary - what was implemented
• evidence.commits - commit hashes (for reference)

If a task's done_summary is empty/missing: Read that task spec's ## Done summary section directly, or infer from git log messages for commits in its evidence.

Parse each completed-task spec for:

• Original acceptance criteria
• Technical approach described
• Variable/function/API names mentioned

Footnotes

1. planSync.crossSpec is the canonical config key. The pre-1.1.3 name planSync.crossEpic was removed in 2.0.0 — flowctl no longer reads it. ↩