agentic-praxis-grimoire

ChatGPT Manager Workflow

Core principle

Select only among ChatGPT top-level-manager capabilities. Use the smallest sufficient capability without creating action or continuation authority.

Do not use

Do not use this subrouter for ordinary Codex planning, design, implementation, debugging, testing, review, worker assignment, synthesis, language, database, or repository work. Do not use it when an explicit applicable ChatGPT-manager leaf is already selected or when no ChatGPT-manager capability is material.

The subrouter does not approve or revise a roadmap, compose the assignment, dispatch an agent, execute work, review or accept a result, or continue automatically. It does not create a mandatory router chain.

Procedure

1. Establish the human-authorized task boundary and applicable repository instructions. Routing cannot broaden either one.
2. Preserve direct explicit selection of an applicable ChatGPT-manager leaf.
3. Read the local capability map. Treat a missing or unreadable map as an integration fault.
4. Exclude this subrouter and every ordinary Codex capability from the candidate set.
5. Read the canonical frontmatter and Do not use section of each materially plausible local leaf.
6. Compare the request with the positive triggers and material non-triggers.
7. Select the smallest sufficient ChatGPT-manager leaf, or select no skill when no local capability applies.
8. State any material overlap, non-trigger, stale metadata, or source ambiguity that affects the result.
9. Hand off to the selected leaf. Do not copy its procedure or execute its work as part of routing.

Ordinary Codex work remains outside this subrouter. The general APG router may select this subrouter for ambiguous ChatGPT-manager selection, but explicit selection needs no router and there is no mandatory router chain.

Project-owned parameters

The human-authorized task and repository own authority, approved roadmaps, manager roles, source qualification, metadata precedence, dispatch, acceptance, continuation, release, and publication policy. The local map owns only the current ChatGPT-manager capability set.

Evidence and completion

A completed routing result identifies the selected ChatGPT-manager leaf or none, the trigger evidence, material non-triggers, and any integration fault. Routing completion does not complete the selected procedure or task.

Stop or escalate

Stop and report the condition when authority is unresolved, the local map or canonical leaf is missing, router metadata is cyclic or cross-domain, duplicate names cannot be source-qualified, an explicit selection conflicts with safety or repository policy, or selection would require invented procedure.

Common mistakes

• Routing ordinary Codex work through the ChatGPT-manager namespace.
• Requiring both routers for an explicit applicable leaf.
• Treating routing as roadmap approval, assignment composition, dispatch, review, acceptance, or continuation.
• Enumerating ordinary APG skills in the local map.
• Selecting several manager leaves merely because later work might use them.
• Inferring source precedence from a duplicate name without client evidence.

This site is open source. Improve this page.