Feature request without a proposal
Use Mind. Forge defines the implementation shape, Council returns build, revise, or stop, and an authorized build can move to Hyper.
Product workflow
Choose the workflow that matches the development stage.
Use Forge to create the proposal, Council to review it, Mind to run the gated proposal-to-implementation path, and Hyper to apply an authorized repository change. Start from the stage you already have. Plain Codex remains enough for small, reversible work with one obvious check.
Idea that still needs design
Use Forge. Five creator lenses turn goals, users, constraints, rollback, and dependencies into one bounded proposal.
Existing proposal or risky diff
Use Council. Isolated roles and anonymous review surface blockers, dissent, unsafe assumptions, and the exact checks still required.
Authorized complex repository change
Use Hyper. Solo handles contained low-risk work; Relay adds bounded read-only investigation and fresh verification around one root writer.
Frontend behavior
Use Council + frontend review, then Hyper. Leonardo critiques UX, Bob records browser evidence, and Hyper applies the authorized fix with executed checks.
Migration, API, data, or concurrency
Use Mind with Deep Council, then Hyper Relay. Keep migration risk, rollback, compatibility, and independent falsification explicit.
Frontend review
Review the experience, then verify the behavior.
Screenshots do not cover focus, keyboard flow, blocked background interaction, or responsive behavior. Frontend review keeps critique and browser evidence separate.
- Leonardo reviews usability, clarity, accessibility, and visual hierarchy.
- Bob operates the browser and records observed behavior; he does not score the proposal.
- A browser result supports the states it exercised, not every possible state.
Mode selection
Pick the smallest mode that catches the risk.
| Situation | Mode | Why |
|---|---|---|
| Small, reversible decision | fast |
A focused Chairman pass without a full role review. |
| Implementation or architecture choice | standard |
Six isolated role prompts, followed by blinded review. Complete reviewer JSON enables deterministic scoring. |
| Irreversible migration, data loss, a close tie | deep |
Additional scrutiny for high-downside decisions; it consumes more Codex usage. |
| Frontend, UX, modals, forms, navigation | standard --frontend-review |
Leonardo reviews the experience; Bob gathers browser evidence when an interactive target is available. |
| Skill or plugin usability | --type skill --skill-review |
Focused review of structure, discoverability, instructions, and operator experience. |
When to skip Council
Use the smallest workflow that covers the risk.
- Use direct Codex for small edits, quick questions, and work with a clear local check.
- Use Council when the decision affects public contracts, persistent data, operations, security, or visible user behavior.
- Use expanded deliberately. It consumes significantly more Codex usage and requires explicit confirmation.