메뉴
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 직업 분류 기준
| 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. |
Create or receive a lease before writing workflow metadata:
kno lease create --nickname "<session-name>"
Bind that lease to every claim, creation, advance, note, and handoff-capsule command you run for the session. Agent identity for notes, handoff capsules, state transitions, and gate decisions comes from the bound lease.
Do not copy legacy --*-agentname/model/version identity flags from telemetry
or command history. They are deprecated, ignored by current kno, and can
leave metadata attributed as [unknown <date>] when no lease is bound.
Run:
kno new "<title>" -d "<description>" --lease <lease-id>
Use a short action-oriented title. Write the description with the expected outcome, relevant context, and constraints for the next agent. Add handoff context for the next actor with:
kno update <id> -H "<capsule>" --lease <lease-id>
Follow this sequence:
kno claim <id> --lease <lease-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> --lease <lease-id>
kno rollback <id> --lease <lease-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.
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.
Cut a new release of foolery by confirming the version bump, syncing the release branch, previewing changes since the last tag, running quality gates, and publishing verified release artifacts.
Configure Foolery by writing a validated ~/.config/foolery/settings.toml and ~/.config/foolery/registry.json. Triggers: `foolery setup`, "configure foolery", "add an agent", "remove an agent", "change dispatch pools", "mount a repo". Works from any frontier agent (Claude, Codex, OpenCode, Gemini, Copilot) — use plain shell verbs, not harness-specific tooling.
Investigate Foolery lease, session, and server logs when asked why an agent turn failed to advance, rolled back unexpectedly, hung, leaked a lease, or skipped lease usage. Use this for the dev server on port 3000, the installed runtime on port 3210, and recent 24-48 hour forensic reviews across both log roots.