grounder-planlisted

Write a named, updatable plan document to the markdown vault for this project. Distill the instruction after `/grounder-plan` into a structured plan — not a chat transcript. Do not dump tool traces, full conversation, or false starts. Build a markdown body with these sections: ```markdown # Plan: <title> ## Goal … ## Steps 1. … 2. … ## Decisions / open questions - … ## Status … ``` **Special case: the instruction asks to view existing plans, not name a new topic** (`list`, `list 3 oldest`, `show plans`, etc.) → run `{{GROUNDER_CLI}} plan list --limit <N> --markdown` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no plan write, no title. Relay the CLI stdout as-is (it already includes the count header; title lines are clickable `[relativePath](fileUri)` links). Otherwise, resolve the target, then **state it plainly before writing** — `Updating plan at <path>.` or `Creating new plan titled <title>.` This is a visible record, not a blocking confirmation — updates overwrite with no `--force`, so get the match right. **1. Known path** (attached/open in chat, or printed by an earlier `grounder plan` this conversation) → update it directly. **2. No path, but update intent** (e.g. "update/continue/revise the plan", or a name that sounds like an existing one) → look it up first: ```bash {{GROUNDER_CLI}} plan list --limit 5 --markdown ``` CLI output starts with a count header, then each res