retitlelisted

# Retitle Give every agent conversation a name that says when it happened, what kind of work it was, and what it was about — in that order, so a sidebar sorts and scans. This skill renames. It never touches what a conversation contains, which project it belongs to, or whether it is pinned, archived, or ordered. ## 1. The scheme ``` MMDD｜TYPE｜subject ``` The separator is the fullwidth vertical line `｜` (U+FF5C), not the ASCII pipe `|`. This is not cosmetic: an ASCII pipe inside a title breaks the very markdown table this skill proposes its renames in, and a title that renders as three broken cells is worse than the name it replaced. Copy the character; do not retype it. No spaces around the separator. `0903｜TWEAK｜batch text rendering`, never `0903 ｜ TWEAK ｜ batch text rendering`. `TYPE` is a closed set of nine, written uppercase. A conversation that fits none of them is not given a tenth — it keeps its original name: | TYPE | Covers | |---|---| | BUILD | New capability, new endpoint, new screen | | SHAPE | Shape decided before code — architecture, interface, layout | | PATCH | Something behaved wrongly and was corrected | | TWEAK | Behaviour was already correct; speed, cost, or clarity improved | | SHIP | Commit, PR, merge, tag, deploy, publish | | PROBE | Tried something to find out what happens; no committed outcome | | WRITE | README, comments, guides, changelogs | | AUDIT | Checked something that already exists against a standard and reported the gaps; nothing buil