RFC tracking: --quick mode for visual-explainer (paired with PR #12)

[mikeyobrien]

Context

Opened RFC PR: #12

This proposes an opt-in --quick mode that keeps default full HTML generation unchanged, while adding a JSON-spec + static-renderer path with fallback to full mode.

Proposal scope

• Preserve default behavior (no flag = current full workflow)
• Add --quick for:
  • /generate-web-diagram
  • /diff-review
  • /plan-review
  • /project-recap
• Fallback to full mode when quick mode fails or is not a fit
• Keep quick output intentionally condensed

Current benchmark/parity signals

• Baseline avg: 165.17s
• Quick v2 avg: 31.42s (~81% faster)
• Estimated output tokens: 7809 -> 1295 (~83% reduction)
• Parity verdict: PASS++++

Feedback requested

• --quick UX is the right flag and behavior
• Fallback policy is explicit/safe enough
• Quick output quality is acceptable for the 4 prompt types
• Bench/parity metrics are sufficient for merge readiness
• Any blockers or must-haves before merge

Exit criteria

• Consensus on quick-mode UX + fallback
• At least one maintainer sign-off on quality/perf tradeoff
• Any blocker items resolved in PR RFC: --quick mode with static renderer + fallback [DO NOT MERGE] #12