✦ You asked for this
Free pack · $0A way to organize a big pile of AI agents, skills and workflows so each request goes to the right one, without loading the whole catalog into every call. A PDF guide and a prompt you can hand to your own orchestrator.
Take me to itfree · PDF and prompt✦ Get it
Free, from Joe Che's AI class. A public guide, a direct-download PDF, and a universal migration prompt you can hand to any orchestrator. The PDF holds the architecture, the visible decision tree, the lane rules and the full migration prompt in one clean file.
✦ The idea
The failure mode is rarely raw model intelligence. It is almost always architecture: too much context, too many ambiguous surfaces, and no clean authority boundary between deterministic operations and judgment-heavy work. This is not about stuffing more intelligence into the prompt. It is about shrinking the top of the system so the runtime can load only what is necessary.
Without this, more agents and more skills eventually make the system slower, noisier and less reliable. With this, requests get routed by lane, execution stays authoritative, and the top of the stack stays tiny.
The outer router chooses the lane. The lane system chooses the executor. That is the whole trick.
Best for repeatable, validated, code-backed actions. If a task is structured, repeatable, and already modeled as an operational recipe, route into the authoritative recipe dispatcher. Do not flatten recipe semantics into generic skill routing.
Best for novel requests, synthesis, and routing uncertainty. This lane handles the work that needs judgment. It can load a selected capability package, compose multiple steps, and explicitly invoke recipes by ID when needed.
Best for explicit orchestration systems like councils, war rooms, or structured review flows. Some capabilities are not recipes and are not ordinary skills. They are reusable orchestration patterns. They need their own lane so they can be discovered without being misclassified.
✦ Use it now
This prompt is written to force an audit-first migration. It makes the system inspect what already exists, preserve deterministic infrastructure, and only then restructure toward the lane-based model. Tap Copy, then paste it to your own orchestrator.
Audit first, plan second, change things only after the plan holds up.
You are the top-level orchestrator for a migration from an ad hoc AI capability system to a lane-based cross-CLI routing architecture. Your job is to inspect the current system first, then produce a migration plan, then execute only after the plan is internally validated. Operate conservatively. Do not rewrite the whole system blindly. Preserve working deterministic infrastructure. Remove ambiguity, not capability. OBJECTIVE Restructure the current system so it follows this shape: ROUTING-SLIM.md -> capabilities index -> lane selector -> lane-native execution The target lanes are: 1. Recipe lane for deterministic, validated, operational execution 2. Worker or skill lane for ambiguous, novel, and compositional work 3. Workflow lane for reusable orchestration patterns PRIMARY OUTCOME The migrated system must become: - smarter at selecting the right capability - faster at startup and routing - leaner in context usage - easier to grow without routing drift - portable across multiple CLIs or orchestrators NON-NEGOTIABLE ARCHITECTURE RULES 1. Keep the bootstrap tiny. ROUTING-SLIM.md must remain a protocol entrypoint, not a catalog dump. 2. Use one generated discovery artifact. Do not hand-maintain a giant central registry. Build one machine-readable index from authoritative local metadata. 3. Route by lane first. Do not flatten recipes, worker skills, and orchestration workflows into one undifferentiated selector. 4. Preserve deterministic recipe systems. If the current system already has a recipe dispatcher, manifest schema, precedence rules, validation logic, or fallback behavior, preserve that lane instead of replacing it. 5. Treat capability packages as the unit. Do not assume everything is a SKILL.md file. Skills, recipes, workflows, agents, prompts, and tool-backed capabilities may all exist in different forms. 6. Exclude non-routable helpers. Utility files, helper modules, and implementation details should not appear in the global routing index unless they are intended to be selected directly. 7. Use immutable IDs. Do not derive stable identity from display names. 8. Prefer deterministic selection before model-heavy selection. The first pass should use explicit metadata, runtime availability, aliases, and routing rules before loading verbose execution docs. DISCOVERY PHASE Before proposing any migration, inspect and classify the current system. Inventory: - recipes - skills - workflows - agents - shared modules - dispatchers - helper utilities - registries - top-level routing files - prompt bundles - direct-download assets - launch automation surfaces if they are part of the capability lifecycle For each discovered item, determine: - what it is - whether it is directly routable - whether it is deterministic or judgment-based - whether it already has an authority boundary - whether it belongs in recipe, worker or skill, or workflow lane - whether it is a helper that should be excluded from routing CURRENT-STATE ANALYSIS Produce a precise diagnosis of the current architecture: - where context bloat comes from - where routing ambiguity comes from - where recipes and skills are being confused - where workflows are hidden or mislabeled - where capability discovery fails - where helper files are leaking into routing surfaces - where naming or alias drift is likely - where central inventory files are overloaded TARGET MODEL Design the target system with these layers: 1. Bootstrap - tiny ROUTING-SLIM.md 2. Discovery - one generated capability index 3. Lane selector - recipe vs worker or skill vs workflow 4. Lane-native executor - authoritative executor inside each lane 5. Normalized result - one result envelope returned to the caller CAPABILITY PACKAGE RULES Define a capability package model that supports: - one canonical ID - one authoritative metadata source adjacent to the capability - one declared lane - one declared type - clear routable vs non-routable status Types may include: - recipe - skill - workflow - worker-backed capability - tool-backed capability - plugin or connector-backed capability RECIPE LANE RULES If recipes already exist: - keep their manifest format authoritative - keep their dispatcher authoritative - keep scoring, validation, precedence, and fallback behavior inside that lane - expose recipes in the global discovery index only for coarse discovery - do not duplicate recipe semantics into the outer routing layer WORKER OR SKILL LANE RULES - select one capability by default - load rich execution docs only after selection - allow explicit composition of recipes when necessary - keep discovery metadata narrow - keep routing logic centralized rather than embedding complex policy into every capability WORKFLOW LANE RULES - treat reusable orchestration patterns as first-class capabilities - do not force them into recipe or ordinary skill categories - define when they are directly invokable and when they are internal-only MIGRATION STRATEGY Do not migrate everything at once. Phase the migration: 1. identify top-level routing and overloaded inventory surfaces 2. identify the existing deterministic lane, if any 3. classify high-frequency capabilities first 4. add authoritative metadata to routable capabilities 5. generate the capability index 6. implement lane selection 7. test with real prompts 8. migrate long-tail capabilities gradually VALIDATION REQUIREMENTS Add validation for: - duplicate IDs - alias collisions - missing or vague routing metadata - missing capability paths - helpers incorrectly exposed as routable - stale generated index - lane/type mismatches TEST REQUIREMENTS Create tests or fixtures for: - deterministic operational requests routing to the recipe lane - ambiguous or novel work routing to the worker or skill lane - explicit orchestration requests routing to the workflow lane - important named capabilities resolving correctly by alias - low-confidence fallback behavior - exclusion of non-routable helpers OUTPUT FORMAT Produce: 1. current-state diagnosis 2. target architecture 3. lane classification table 4. migration phases 5. validation rules 6. test cases 7. implementation checklist IMPORTANT BEHAVIOR - Do not start by mutating files. - Audit first. - Preserve working deterministic infrastructure. - Keep the top of the system tiny. - Expand only as necessary. - Optimize for portability across different CLIs and orchestrators. - Optimize for long-term maintainability, not cleverness. If the current system already contains a dispatcher, giveaway pipeline, registry, workflow runner, or orchestration layer, classify it before changing it.
✦ Get unstuck
The PDF is the guide: the architecture, the decision tree, the lane rules and the full prompt. The prompt file is only the migration prompt, ready to hand to your own orchestrator.
Tap Download the PDF again in a normal browser tab. The same ideas, and the full prompt, are also on this page.
Hand it to your orchestrator: the top-level AI that runs your agents, skills and workflows. The prompt is written to that role. It is meant to work across different CLIs and orchestrators.
No. The prompt tells the AI to inspect the current system first, produce a migration plan, and only then execute once the plan is validated. It also says not to start by mutating files.
The recipe lane is for repeatable, validated, code-backed work. The worker or skill lane is for ambiguous, new or mixed work that needs judgment. The workflow lane is for named orchestration patterns, like a council or a structured review flow.
The prompt says not to migrate everything at once. The phases start with the busiest capabilities and leave the long tail for later. Ask it to follow those phases.
Email joe@mastermindshq.business. Say which step you were on and paste what you saw.
✦ What next · paid · optional

You came for one piece of my Claude Code setup. If you have your own website, the next useful job for that setup is getting the site found.
Get your website listed on Google and Bing so people (and ChatGPT) can find you by your name and your service. ChatGPT finds websites mostly through Bing, so we tell Bing about you too. Your own Claude Code does the work on your computer, one prompt at a time.
Not for you? Close this page. Everything above stays free.
Created by Joe Che.
ChatGPT is a trademark of OpenAI. Claude is a trademark of Anthropic. This page is not affiliated with either.