predict

# `predict` — Pre-Implementation Multi-Persona Analysis Structured pre-implementation review. Five expert personas assess the proposal **independently**, then debate, then converge on a verdict with a confidence score. Surfacing architectural, security, performance, and UX flaws before the first commit is the cheapest place to catch them. --- ## When to invoke Use before implementing any of: - A new transport strategy (`sapisidhash`, `cdp_attach`, `official_veo`) - Auth flow changes (new strategy, G12 bypass technique, cookie extraction) - Selector cascade redesigns affecting `ONBOARDING_SELECTORS`, `NEW_PROJECT_SELECTORS`, `FRAME_SLOTS_STRUCT` - Schema migrations in `gflow_cli/data/` - New CLI surface or exit-code changes - Any backlog item with an "investigation gate" in PLAN.md before coding Skip for: trivial bug fixes (< 10 lines, isolated, no boundary cross), already-approved PLAN.md tasks entering EXECUTE, pure doc changes. --- ## Invocation ``` /gflow:predict <proposal> ``` `<proposal>` is a short description of what you intend to build or change — one paragraph is enough. Examples: - "Wire SAPISIDHASH auth header into `_post_json` for all `aisandbox-pa` routes (Issue #15)" - "Add CDP-attach transport as opt-in `--transport cdp_attach` alongside `ui_automation`" - "Redesign `gflow video batch` to use a local manifest ledger for skip-already-done" - "Add `AuthBrowserBlockedError` to `internal_chromium.py` when Google rejects bundled Chromium" --- ## Protocol ...