TachiBot/Docs
HomeGitHubnpm
IntroductionInstallationQuick StartExamplesTools OverviewPlannerPrompt TechniquesWorkflowsPingPongTool ProfilesTools ConfigThemesUsage StatsAPI KeysWhat's NewTerms & ConditionsCookie Policy
Products
TachiBot MCPdokorotachi-agent
Getting started
  • Introduction
  • Installation
  • Quick Start
  • Examples
Core features
  • Tools Overview
  • Planner
  • Prompt Techniques
  • Workflows
  • PingPong
Configuration
  • Tool Profiles
  • Tools Config
  • Themes
  • Usage Stats
  • API Keys
Resources
  • What's New
Legal
  • Terms & Conditions
  • Cookie Policy

Loading documentation...

← Previous
Tools Overview
Next →
Prompt Techniques
Edit this page on GitHub
Docs/Core features

Multi-Model Planner

Verified implementation plans from a council of models. Grok searches, Qwen analyzes code, Kimi reasons step-by-step, GPT critiques, Gemini scores.

What is the Planner?

Instead of asking one model for a plan, TachiBot runs your task through 9–13 specialized steps across 6 models.

  1. Grok Searchgrounds truth with real-time web data
  2. Qwen Coderanalyzes code, APIs, dependencies
  3. Kimi K3 · reasoningtraces execution flows step by step
  4. Kimi K3 · decompositionsubtasks with IDs, dependencies, acceptance criteria
  5. GPT-5.6 · criticfinds gaps, failure modes, security issues
  6. Qwen3.8 Maxfirst synthesis with quality scores
  7. Gemini 3.1 Pro · final judgenumbered steps, success criteria, confidence
Optional phases are auto-detected: UX analysis for UI tasks (WCAG 2.1 AA), responsive design for layout tasks.
i
Why not just ask Claude to make a plan?
A single model can confidently plan around outdated libraries, deprecated APIs, or patterns it invented. The Planner grounds every plan in search data, cross-checks it, and scores confidence first.

Key benefits

Grounded in real data
Current best practices and docs before any analysis.
Multi-perspective
Six models catch different kinds of errors.
Code-aware
Pass your actual code; plans fit your architecture.
Quality scored
Code quality, security, performance and confidence.
Checkpoints
Verification at 50%, 80% (kimi_decompose) and 100%.
Saved automatically
Plans persist to devlog.

How to use

A coordinator pattern: each call returns one tool to execute. Run it, pass the result back, get the next instruction — so you see every step and can interrupt.

planner.tsts
1planner_maker({
2 task: "Add real-time collaboration to the dashboard",
3 mode: "start"
4})
5// Returns: instruction to run grok_search
6
7planner_maker({
8 task: "Add real-time collaboration to the dashboard",
9 mode: "continue",
10 step: 2,
11 prior: { search: "[grok_search output]" }
12})
13// Repeat until isComplete: true

Run the plan

planner_runner executes plans against goal-oriented verification gates. list_plans shows recent plans.

runner.tsts
1planner_runner({ plan: planContent, mode: "step", stepNum: 1 })