EPURE User Journey: All Your Actions Aligned in Column 1 (Top to Bottom) Diagram

Column 1 — All Your Actions (Top to Bottom)

Steps 1 & 2: Post /epure plan, reply to Grill questions, run /epure to-spec, and comment in plain text to edit the spec
Steps 3 & 4: Run /epure to-tickets then /epure approve; only step in during Step 4 (/epure sync or /epure continue) on conflict or escalation
Step 5: Once all checks on the final feature/* -> dev PR are green, click Squash & Merge then dispatch the release

Columns 2 & 3 — Automation, Exchanges & Autofix

Behind the scenes (Col 2): Zero-context Goldfish audit on plan/*, sub_issues + blocked_by DAG, direct plan/* -> feature/* merge + spec_sha lock
Exchanges & Edits (Col 3): Free-text comments during Grill and Spec; during the DAG, automatic Autofix (1..3 tries) on Stage 1, CI, or Review
Git Sync & Convergence: /epure sync resolves dev -> feature/* -> task/* conflicts 3-way; EpicConvergenceAudit triggers an automatic Phase 2 if needed

Column 4 — GitHub Feedback & When to Act

At every framing milestone (Grill settled, Spec committed, DAG created), EPURE posts a comment naming the exact next command to run
During DAG execution (Step 4), 0 action is needed while Autofix (1..3 tries) and event-driven async CI progress
If a ticket exceeds 3 attempts or touches a sensitive path, EPURE applies the needs-human label and waits for /epure continue