菜单
Retire a ticket on the owner's word, at any status. Moves it into ../docs/done/, updates the README and both plan files, syncs any page the change made false, reranks the live work and reads the running order back. Use when the owner says a ticket works, says "mark it done", or says "close the ticket".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ryanallen/leaftext --skill done命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Rank every live ticket into ../docs/PLAN.md and keep the shipped, canceled and on-hold folders true. Wrong today first, then dependencies, then cost; only the owner moves work on or off hold. Use when the user says "what should I build next", "rank the tickets", "make a plan", "priorities", or hands over the plan folder to be brought up to date.
Write a ticket — a Markdown plan with phases and a checkbox per piece of work, filed in a subject folder under ../docs/features/, ../docs/refactor/ or ../docs/fixes/. Reads ../docs/README.md first so it never re-plans what the tree already answered, writes that README row in the same pass, then runs /pm to rank the new ticket. It researches the code and records options; /design makes the decisions. Use when the user says "write a ticket", "make a plan for", "spec this out", hands over work to be scoped rather than built, or asks what plans already exist.
Design a ticket before anyone builds it. Watches the fault happen in a running copy before it will name a cause — and where nothing can watch it, files the tooling that would as a ticket in front of this one rather than guessing. Then opens every line it cites against the code, holds the plan against the rules this repo already paid for, fixes what is wrong in place, draws it — a photographed wireframe where it touches the window, a flow where it does not, and never a ticket left with no picture — dates the top of the file, and records what was wrong at the bottom. Never edits app code. Use when the user says "design this ticket", "review this plan", "check this ticket", or hands over a Markdown plan written by /ticket.
正在显示 SKILL.md
| name | done |
| description | Retire a ticket on the owner's word, at any status. Moves it into ../docs/done/, updates the README and both plan files, syncs any page the change made false, reranks the live work and reads the running order back. Use when the owner says a ticket works, says "mark it done", or says "close the ticket". |
| argument-hint | [ticket path] |
| user-invocable | true |
Retire a ticket on the owner's word. Closing is the owner's call. Never refuse and never infer it. Any status closes, open boxes and all.
A struck owner's box is not the owner's word. It says the subject has nothing to press; it does not say the owner has seen what was built. So /dev never runs this skill, a plan carrying one stays live until the owner asks, and /check leaves it alone.
Two sessions build in this one checkout, on tickets the running order's Devs with column says share no file, and neither of them writes the running order. This pass is one of the two that do write it, which is why it never runs beside a build.
Another session's work is not this pass's, whatever state it is in. A ticket this pass was not pointed at is not stale, not repaired, not re-filed and not retired alongside the one it was — however its boxes read, and however finished it looks — because the session holding it is already its record and a second hand on it writes over the first.
With no argument, take a live ticket at Released.
Add > **Shipped 18 August 2026, 9:11pm, v1.21.2.** and keep the dated Designed line.
Move the ticket into the matching folder under ../docs/done/ and fix its relative links. Take the links pointing at it with it: search both trees for its file name and repoint every one, or /check fails naming each.
Rewrite its README row to say what shipped, and move it out of the live half into the ## Shipped table for its subject — the index is navigated by heading, so a row left where it was reads as work that is waiting however its words are rewritten. Seven sat that way at once. scripts/check-plan.mjs refuses one now, naming the heading it belongs under.
Remove its live row from ../docs/PLAN.md and move it into ../docs/done/PLAN.md, its Status cell rewritten to the date and time it closed. This pass and /pm are the live running order's only writers, and neither runs beside a build — it is one ranked list, two rewrites of it are not something any merge can settle, and it is the one file the Devs with column cannot promise a pair is safe over. A live cell is otherwise computed, so nothing here types a stage in by hand. It lands inside the ## Retired from tier N table for the tier its live row sat in, in that table's own closing order and with a cell for every column that table's header names — a tier with no table there yet gets one. Never above the file's title: that file is read by the tier a row was retired from, and a row dropped at the top belongs to no tier and sits under no header, which is how 30 of them once came to open it. Empty a tier that its going leaves with no rows. Keep the live file starting with its title, # Leaftext Plan Log, and its first work table the first thing under it; put its count line, summary, and other notes after the work tables.
Sync any published page made false by the change — the development pages included, when the work added a test subject file, a check, or changed how a skill works. Run /sync-docs, and /code-comments where this pass touched a comment.
This pass runs no complete gate. The ticket being retired here already shipped, and its code was proved at the end of its build — so the suite would prove the same bytes a third time. What this pass writes is pages and plan rows, and step 7 reads the plan back.
Run /pm after the retirement edits and checks. Its Devs with bundler removes the retired ticket from every remaining cell, and its authored rewrite puts every remaining row back in order.
Read both plan files after /pm. Stop if the retired ticket still appears in ../docs/PLAN.md, is absent from ../docs/done/PLAN.md, any remaining position is stale, or the live plan's Last ranked stamp is older than the shipped note.
This is two files read against each other, and it is never a report. Nothing it finds reaches the owner: a disagreement stops the pass and is fixed here, and the reply is the owner's own message, word for word, exactly as it would be with nothing found at all.
Every date this pass writes carries the time beside it — the shipped note, the README row, the Status cell of the retired row — read off this machine's clock (Get-Date) as it is written. Several tickets close in one afternoon, and a day is the same six words on all of them, so nothing says which shipped first or how long ago the last one did. AGENTS.md holds the rule; just check-docs refuses a date written from 2026-08-19 on with no time after it.
Do not run git. Where a box never shipped, strike it with what is missing, so the file does not claim it.
The whole reply is the owner's message, word for word.
Anything this pass finds that it is not here to do is a ticket, written before the hand-back — /ticket, its row in ../docs/README.md, /pm.
Anything the work in front of this pass hints could be faster is a performance finding: file it as a ticket in the same turn, without stopping for a benchmark or fixing it in passing, and never name it in the reply. Retirement sees the plan-tree rewrites together, so repeated work, an unnecessarily broad read or a wait is enough to file while this pass finishes the owner's close.
