菜单
Use the Knots workflow through `kno` when asked to create a knot, work on a specific knot, claim or execute a knot, advance a knot to its next state, or recover or roll back a knot safely after blocked or failed work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use the Knots workflow through `kno` when asked to create a new knot from a rough request and you need a concise goal, exact acceptance criteria, and repeatable verification steps.
Use the Knots workflow through `kno` when asked to drive a knot end to end, run a claimed knot to completion, or keep advancing a knot until it reaches a terminal state such as `SHIPPED`, or a passive waiting state such as `BLOCKED` or `DEFERRED`.
Use the Knots workflow through `kno` when asked to orchestrate an execution plan from start to finish, processing waves sequentially, steps within each wave sequentially, and launching knots within each step concurrently.
Release a new version of Loom — bumps version, runs checks, tags, and pushes
| name | knots |
| description | Use the Knots workflow through `kno` when asked to create a knot, work on a specific knot, claim or execute a knot, advance a knot to its next state, or recover or roll back a knot safely after blocked or failed work. |
Run:
kno new "<title>" -d "<description>"
Use a short action-oriented title. Write the description with the expected outcome, relevant context, and constraints for the next agent.
Follow this sequence:
kno claim <id>
kno -C <path_to_repo> ... because Knots is installed for the repo root,
not the worktree path.kno next <id> --expected-state <current_state>
kno rollback <id>
If the claimed knot lists children, handle the children first:
Do not invent alternate transition workflows. Prefer claim, next, and
rollback over manual state mutation unless the user explicitly asks for it.