add-plan-authoringlisted

# Plan Authoring <!-- uses: - agent: plan-review-agent - skill: add-review-discipline - skill: add-final-report - skill: add-plan-authoring/references/plan-template.md - mention: add-build-ledger - mention: /add-framework--done - mention: /add-framework--build --> Owns the plan DOCUMENT. What the plan decides is the planning command's job; how it is named, shaped, reviewed and delivered is here. ## When to Use - Writing a new plan, or revising one. - Resolving a plan argument (Continue Mode) or listing plans (List Mode). - Dispatching the plan reviewer and acting on its verdict. ## When NOT to Use - Executing a plan. That is the build side — load `add-build-ledger`. --- ## File Naming Two documents are named here, and they share one timestamp rule: | Document | Path | |---|---| | The plan | `docs/plans/YYYY-MM-DDTHHMMSS-PLAN--<slug>.md` | | The changelog | `docs/changelog/YYYY-MM-DDTHHMMSS-<verb>-<slug>.md` | Timestamp in **local time**, `T` between date and time, **no separators inside `HHMMSS`** — Windows forbids `:` in a filename. Lexicographic sort therefore equals chronological sort. `<verb>` is `add` | `update` | `refactor` | `remove` | `fix`. **It survives the timestamp**: once the timestamp leads it no longer affects order, and it is information the files already carry. The date alone did not sort — a day with several deliveries alphabetised by verb, and the directory holds days that did. ⛔ **Pre-existing changelogs keep the names they were written with**