用 Jev 给 Opus 5.5 子 agent 分配任务与算力档位

Avid @Av1dlive原推发布于 2026.09.26

在 X 上打开原推

i finally mastered how to maximise my opus 5.5 usage limits... the trick: let jev choose which subagent gets each task and how much effort it should use. [here’s how i’d wire it:] claude breaks the project into tasks. jev selects from predefined worker profiles. claude applies the selected settings and dispatches the work. → main session, medium: clarify the requirements, define what “done” looks like, and prepare the tasks → builder, low: small, clearly defined tasks with existing examples or patterns → builder, medium: tasks that connect multiple parts or need decisions within the approved plan → verifier, high: check requirements, probe edge cases, and report problems for the builder to fix jev gets the task’s scope, what’s uncertain, and the consequences of failure. it chooses from the profiles allowed for that task. your approval checkpoints stay in place. paste this into your next planning session: “use opus 5.5 with jev selecting the worker and effort profile for each task. first, check that a working jev integration is available and that this environment supports separate effort settings for subagents. check for configuration or environment overrides that could prevent those settings from taking effect. if anything is missing, explain what needs wiring before proceeding. break my request into tasks with clear ownership, dependencies, relevant context, and acceptance checks. keep small related tasks together when a separate subagent would add unnecessary overhead. keep the main session at medium effort. offer jev these worker profiles: builder at low effort for small, clearly defined tasks using existing patterns; builder at medium effort for tasks that connect multiple parts or require decisions within the approved plan; verifier at high effort for checking requirements and edge cases. give jev each task’s scope, uncertainties, dependencies, and consequences of failure. only offer profiles appropriate to the current stage. validate its selection before dispatching. use the actual jev integration; don’t simulate its decisions. if it abstains or returns an invalid choice, stop that handoff and ask me. show me the task plan and proposed assignments before starting. after approval, launch the selected workers with their assigned effort settings, relevant context, file ownership, and completion checks. let me review the result before verification. the verifier may add tests but must leave implementation code unchanged. have it report what passed, what failed, and what remains uncertain. send implementation fixes back to the builder, then recheck the affected parts. if a task repeatedly fails, examine the requirements and approach before increasing effort. report available total usage, including jev calls, worker calls, retries, and verification. don’t invent missing data. compare similar completed tasks before claiming savings.” steal this 👇

这条是引用着另一条写的：「一篇上手 Jev 的完整构建指南：代码、架构与图」