post_intent
Register your planned work and file paths to prevent other agents from colliding. Get a unique intent ID and collision warnings before starting any non-trivial coding task.
Instructions
Register what you are about to work on so other developers' agents can avoid collisions. Call this before starting any non-trivial coding task (anything touching more than a trivial fix). Infer kind: build for work meant to land, explore/spike for throwaway investigation, decision for a resolved decision worth recording (post it the moment a debate settles: pass the resolution in outcome — what was decided, what was rejected, and why; no touches needed; it is stored complete, never collides, and needs no complete_intent). Infer touches from your plan as repo-relative glob patterns. Returns the intent id — keep it to post the outcome later. Also returns any overlapping in-flight intents — active work (alert warn/nudge/fyi) and recently-completed work that may not have landed in git yet (always fyi): overlaps are the COLLISION signal — if overlap level is warn, tell your user before proceeding; for fyi, check whether that work is already in your tree before redoing it. The response also includes context — recently-completed work relevant to THIS task: read those outcomes before you start, the surprises and dead ends in them are load-bearing (a rejected approach you might retry, a gotcha you will hit).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | build = meant to land; explore/spike = throwaway investigation; decision = a resolved decision recorded for the feed (requires `outcome`). | build |
| repo | Yes | Repository name, e.g. 'raveneye'. Use the basename of the git origin remote (or the repo root directory name if there is no remote) — every agent on the same repo must derive the same string or collision checks silently miss each other. | |
| title | No | Short headline for the work, ≤80 chars, like a commit subject line (e.g. 'FTS5 search + recall mode'). Cheap to write and the feed reads far better with one — provide it. | |
| branch | No | Git branch, if known. | |
| outcome | No | kind=decision only: the resolution — what was decided, what was rejected, and why. Other kinds write outcomes at completion instead. | |
| summary | Yes | One paragraph: what you're doing and why. | |
| touches | Yes | Repo-relative glob patterns you expect to touch, e.g. ['central/services/scorecard*']. |