メニュー
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`.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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 orchestrate an execution plan from start to finish, processing waves sequentially, steps within each wave sequentially, and launching knots within each step concurrently.
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.
Release a new version of Loom — bumps version, runs checks, tags, and pushes
SOC 職業分類に基づく
| name | knots-e2e |
| description | 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`. |
Follow this sequence:
kno claim <id>
kno -C <path_to_repo> ... because Knots is installed for the repo root,
not the worktree path.SHIPPED, BLOCKED, or DEFERRED, stop cleanly.kno next <id> --expected-state <current_state>
kno next output.SHIPPED,
BLOCKED, or DEFERRED.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.
Do not use kno show as the primary control-flow source when claim/next
already provide the state needed to continue safely.