Live Progress Tracking and Inline Commenting

The Plan Wizard provides live progress tracking and inline commenting for collaboration, creating a seamless feedback loop between you and Vex. These features transform the Plan Wizard from a passive monitoring tool into an active collaboration interface.

Live progress tracking:

The Plan Wizard shows you exactly what Vex is doing right now:

• Progress bars — Visual percentage completion for each phase, feature, and overall plan. Bars fill smoothly as tasks complete.
• Status colors — Color-coded badges make status instantly recognizable:
  • Green (completed) — Task finished and verified
  • Cyan (in progress) — Vex is actively working on this task
  • Yellow (pending) — Task queued but not started
  • Red (blocked) — Task cannot proceed due to dependency or error
  • Gray (cancelled) — Task was skipped or plan was cancelled
• Loop step indicators — Shows which of the 9 implementation stages Vex is in:
  • 0: Context Load — Loading relevant files and understanding requirements
  • 1: Discovery — Using workspace.find to locate existing code
  • 2: Plan — Creating detailed implementation steps
  • 3: Dry-Run — Simulating file operations to preview changes
  • 4: Execute — Actually creating/modifying files
  • 5: Verify — Checking that changes compiled successfully
  • 6: Test — Running validation checks
  • 7: Document — Adding comments and documentation
  • 8: Sign-off — Marking task complete and moving to next
• Real-time updates — Changes appear within seconds as Vex works. The UI updates smoothly without flickering.
• Time tracking — See how long each task has been in progress and estimate completion time
• Dependency visualization — See which tasks are blocked waiting for others to complete

Inline commenting:

Inline commenting lets you provide feedback to Vex without interrupting the workflow. Here’s how it works:

1. Click on any task in the Active Plans hierarchy — The task details panel opens on the right
2. Type your comment in the comment field — A text area appears below the task description
3. Click “Add Comment” — Your comment is saved immediately
4. Comment is saved to the database with timestamp — Stored in the gc_plan_comments table
5. Vex must acknowledge the comment before advancing to the next task (hard gate) — This is a blocking requirement
6. Vex responds with acknowledge_comment, creating a threaded conversation — You see Vex’s acknowledgment in the comment thread

Comment use cases:

Comments are versatile. Use them for:

• “Change the player speed to 10 instead of 5” — Request specific value changes
• “Use a different shader for this material” — Suggest alternative approaches
• “Skip this task, I’ll do it manually” — Take over implementation yourself
• “Great work on this feature!” — Provide positive feedback (Vex appreciates encouragement)
• “This script has a bug in line 47” — Report issues for Vex to fix
• “Add error handling for null references” — Request additional functionality

Comment acknowledgment gate:

If you leave a comment on a task, Vex cannot advance past that task until it acknowledges your comment. This ensures your feedback is never ignored. The acknowledgment gate works like this:

1. You add a comment to Task 5
2. Vex completes Task 5
3. Vex attempts to move to Task 6
4. GameCatalyst checks: “Does Task 5 have unacknowledged comments?”
5. If yes: Vex is blocked and must call workspace.plan action=acknowledge_comment
6. Vex reads your comment and responds
7. Gate opens, Vex proceeds to Task 6

This hard gate ensures you and Vex stay synchronized. No comment goes unread. No feedback gets lost.