Split a task across models
planSplit a multi-part task into routed parts with cost, time and model for each, letting Leanfare run the simple ones on cheaper or free models so your plan lasts longer.
Instructions
Before a task with several parts (a feature, a fix across files, a refactor, research across many files, reverse engineering a project), ask Leanfare how to split it. It answers with a short table: each part, its kind, where it runs (you, or Leanfare on a local, free or pay per use model), the model, about how long, the tokens it keeps out of the user's plan, and the cost; then what to do next. Leanfare starts its own parts at once by itself (local and free ones, paid ones within the user's cap) and this answers with those that finish within about 25 seconds: do not run them again with delegate. Do the parts it leaves to you, then call plan_status with the plan's id (wait 50) for the rest of Leanfare's answers, and review and grade each. Name the files or folders the task is about in files: here Leanfare only measures them, it reads them when delegate runs a part. A model the user ticked does the split (a few cents or less, $0 on free models; one that takes more than 40 seconds is let go, and the rules split it); split rules makes it by rules, with no model.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| run | No | false: only split the task; Leanfare runs nothing. By default Leanfare starts its parts at once. | |
| task | Yes | The whole task, as the user gave it, with what you already know about it. | |
| files | No | The files or folders the task is about: full paths, ~/ paths, or paths relative to folder. Only their names and sizes are used here. | |
| level | No | The Leanfare level for this chat or session, as the level tool or Leanfare's prompt line gave it. Leave it out when none was given. | |
| parts | No | At levels 1 to 4, your own split: the task in parts, each with its kind (code changes the project; act needs your own tools), effort, the parts it needs and the files it reads (named as in files). Leanfare places each part. At level 5 leave it out: Leanfare's model makes the split. | |
| split | No | auto (the default): a model the user ticked splits it. rules: Leanfare splits it by rules, with no model call. | |
| checks | No | Once per project: the short list of cheap checks its work must pass, kept for the folder and shown with every plan made there. Each a line: "run: bun test" (a command you run yourself at the end), "words: utilize, leverage" (words Leanfare keeps out of what comes back, checked by itself) or anything to look at ("the Savings page fits one screen"). Giving it again replaces the list. Needs the project's folder. | |
| folder | No | The folder relative paths start from. By default, the folder the MCP client started Leanfare in (in Claude Code, the project). | |
| private | No | true keeps the whole plan on the user's computer: the split and every Leanfare part go only to models there (Ollama), and a part none of them can take stays with you. Use it for anything sensitive or personal, or when the user asks. | |
| your_model | No | The model you run on, as your own instructions name it (for example claude-opus-5-5). Leanfare names it for the work that stays with you, and the report shows it as the prompt's main model. | |
| your_effort | No | The thinking effort you run at, when you know it. The report shows it with your model. |