Choose the next agent workflow

Provides a bottleneck-driven agent prompt and an eleven-step workflow connecting context, shell visibility, routing, composition, verified variations, evidence, delegation, council critique, and human selection.

Use this as the map for the full workflow. Each section stands alone, but the sequence is deliberate.

Agent Setup Prompt

Use this workflow index to choose the next agent move for a software project.

First identify the current bottleneck:
- missing context
- missing shell tools
- unclear helper behavior
- wrong workspace or session
- weak prompt shape
- too many plausible implementations
- video or runtime evidence to analyze
- bounded debug packet to preserve
- narrow task to delegate
- risky decision that needs independent model critique
- generated options that need a human pick

Then pick the matching section and ask the agent to follow that workflow. Keep the request concrete: name the repo, the bug or decision, the files or logs to inspect, and the proof you expect before the work is considered done.

Phase Map

Phase 1: Context And Environment

Make invisible project context and agent shell context explicit before asking for work.

  1. Pack context when broad code reasoning needs Oracle.
  2. Make the shell and tools visible to Codex.
  3. Classify zsh helper names and fallback boundaries.

Transition: Once the agent can see the right context and tool surface, route the work to the right place before launch.

Phase 2: Routing And Composition

Put work in the right workspace, pane, session, and prompt shape before it runs.

  1. Route the right pane/session.
  2. Compose before launch.

Transition: Once launch is deliberate, use the agent surface to produce, compare, and preserve evidence.

Phase 3: Generation And Evidence

Generate useful options and turn rich runtime or media evidence into prompt material.

  1. Generate verified variations.
  2. Use video as prompt material.
  3. Mark debug moments with bounded evidence.

Transition: Once the work is bounded and evidenced, delegate narrow packets or ask for independent review.

Phase 4: Delegation And Review

Hand small tool-shaped work to narrow agents, use councils for expensive decisions, and capture human choices before implementation.

  1. Hand tool-shaped packets to narrow Imps.
  2. Ask a model council when independent disagreement improves a risky decision.
  3. Capture a phone-friendly human selection from generated options and resume from saved JSON.

Section Map

Phase Section Workflow Move File
Context And Environment 1 Pack context when broad code reasoning needs Oracle 01-oracle-packing-context.md
Context And Environment 2 Make the shell and tools visible to Codex 02-loading-zsh-env-into-codex.md
Context And Environment 3 Classify zsh helper names and fallback boundaries 03-zsh-functions-aliases.md
Routing And Composition 4 Route the right pane/session 04-agentic-dev-environment-orchestrator.md
Routing And Composition 5 Compose before launch 05-prompt-builder.md
Generation And Evidence 6 Generate verified variations 06-code-is-free-generate-variations.md
Generation And Evidence 7 Use video as prompt material 07-video-as-prompts.md
Generation And Evidence 8 Mark debug moments with bounded evidence 08-debugging-with-agent-markers.md
Delegation And Review 9 Hand tool-shaped packets to narrow Imps 09-imps.md
Delegation And Review 10 Ask a model council when independent disagreement improves a risky decision 10-fusion-model-council.md
Delegation And Review 11 Capture a phone-friendly human selection from generated options 11-web-choices.md

How To Use The Set

Start with the section that matches the current bottleneck:

Bottleneck Start With
The agent needs a broad codebase answer Section 1
A command works locally but not in Codex Section 2
A helper name is unclear or shell-only Section 3
Work is landing in the wrong pane or session Section 4
The prompt needs shaping before launch Section 5
Several implementations are plausible Section 6
A recording contains the missing context Section 7
Logs exist but the important moment is unclear Section 8
The task is mostly one command-line tool Section 9
Several strong models may disagree on a risky architecture or implementation choice Section 10
The agent generated good options but needs a human pick or feedback before continuing Section 11

Section 10 is especially useful after Section 6 for comparing strategies, or after Section 9 when a bounded packet needs independent review before a risky implementation choice. Section 11 is especially useful after Section 6 or Section 10 when generated options need a human selection, ranking, or feedback before implementation continues.

Source references