Plan a project route
plan_projectRoute from presale to closure for a project context. Default is compact (ids by strength + a names dictionary, core items and gate evidence for all stages, about 6–10k characters). Ask for one stage with stages:['st.design'] and format:'full' for reasons, avoid texts and gate details. 'core' = do it here (context rule, flag or gate-critical artifact), at most 8 work items per stage (producers of the gate's critical artifacts first, then context rules, then flags).
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "plan_project"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Answer language, default en | |
| format | No | Default compact | |
| stages | No | Stage ids or codes, e.g. ['st.analysis','design']. Default: all | |
| context | No | Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data. | |
| include | No | Default all four | |
| min_strength | No | Default: core for all stages, all when stages are given |