Flow Revise

Update spec or plan when implementation reveals issues.

Usage

flow-revise <flow_id>

Workflow

Phase 1: Load Current State

Read .agent/specs/{flow_id}/:

• spec.md
• learnings.md

Phase 2: Identify Revision Type

Ask user: Spec, Plan, or Both?

Phase 3: Document Reason

Log why revision is needed.

Phase 4: Make Changes

Update spec.md as needed.

Phase 5: Log Revision

Append to .agent/specs/{flow_id}/revisions.md:

## [YYYY-MM-DD HH:MM] Revision {N}

**Type:** {spec|plan|both}
**Reason:** {reason}
**Changes:** {description}

Phase 6: Sync Beads

br update {affected_task_ids} --notes "Revised: {reason}"

# If NEW tasks added:
br create "{new_task}" --parent {epic_id} -p 2 \
  --description="{what_and_why}"
br update {new_task_id} --notes "Added during revision. Created by flow-revise"

Critical Rules

1. LOG EVERYTHING - All revisions documented
2. BEADS SYNC - Update affected tasks
3. PRESERVE HISTORY - Never delete, only append