atlas_plan
Idempotent
Create a new open Work Order in local docs with linked spec section, implementing files, and checklist steps to structure feature plans before coding.
Instructions
Create a new ⬜ OPEN Work Order in local documentation, automatically linking the matching spec section (atlas_where), implements: files, and - [ ] checklist steps.
Use this tool when planning a new feature or breaking a user request into structured steps before coding.
Unlike `atlas_publish` (which records a finished result), `atlas_plan` assigns the next free Work Order
number, looks up the relevant spec anchor via BM25 search, and writes a checkable `- [ ]` step list.
Behavior & Output:
- Queries the documentation index for `topic`, attaches `Spec <anchor> (<path>:<line>)` and any `implements:` files.
- Writes `Work Order <N> — ⬜ OPEN (<topic>): ...` plus `- [ ] <step>` lines into `docs/ARCHITECTURE.md`.
- Pre-records `verify_symbols` in `.atlas/wo-symbols.yml` when provided.
- Returns JSON `{written, verified, wo, title, spec_anchor, spec_origin, implements, steps, line}`.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"topic": "<topic>"
},
"name": "atlas_plan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wo | No | Optional explicit Work Order number. Omit or pass null to automatically assign the next free Work Order number. | |
| steps | No | Optional list of concrete implementation steps to record as `- [ ]` checkboxes under the Work Order (e.g. ['Apply burn stacks in effects.py', 'Call tick_effects at end of turn', 'Add unit test']). All steps must be checked off via `atlas_set_status(task=..., status='done')` before the Work Order can be marked done. | |
| topic | Yes | Title or topic of the Work Order to create (e.g. 'Damage Over Time' or 'Dialogue conditions'). Automatically searched against the documentation index (`atlas_where`) to link the matching spec anchor and `implements:` files. | |
| verify_symbols | No | Optional list of target function or class names expected from this Work Order (pre-registered in `.atlas/wo-symbols.yml` so the wiring gate enforces them on completion). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |