Feedback infra rewrites plan then opus workers

For rewrites of forge infrastructure (scripts, automations, the chat.justinsforge surface, skills): the coordinator (Fable) plans the work, presents the plan to Justin, and only after his approval spawns 2-3 OPUS workers to execute. Stated 2026-07-12 during the first live dev-queue coordinator session.

Why: Infra changes have blast radius across every future session; Justin wants a review gate on the design, and he judges opus worth the cost for infra-quality execution. This refines [[feedback_wda_model_tiering]] (sonnet/haiku stays the default for routine app-feature workers); opus is also the right tier when Justin explicitly escalates a gnarly root-cause bug (e.g. the CreatorTrack icon-sync bug, 2026-07-12).

How to apply: When a task touches forge scripts/, .claude/skills/, automations, or the chat surface: write the plan to memory/plans/-YYYY-MM-DD.md (feature-plan house format), present a summary, wait for approval, then execute with 2-3 opus workers (Workflow agent(..., {model: 'opus'}) or Agent model: 'opus'). CreatorTrack app-feature work through the dev queue keeps sonnet workers unless Justin escalates.

URL: https://mkdocs.justinsforge.com/memory/general/feedback_infra_rewrites_plan_then_opus_workers/

[Claude Code]