メニュー
Transition the active unit to a new lifecycle status. Use when declaring the unit shipped, archived, abandoned, handed-off, or deprecated. Terminal transitions require every required phase to be resolved, or a forced override with rationale.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Record a named human reviewer's approval (or rejection) of a prior event on the active unit. Use for human-in-the-loop sign-off on gate decisions, status transitions, or milestone ships — never for agent self-review. Emits `ApprovalRecorded` with a bounded rationale so audits surface the signature instead of hunting through prose.
Read the current state of a unit — current phase, status, shipped milestones, model timeline — or find units that match a predicate. Works for active, archived, abandoned, and handed-off units alike (projections are pure historical reads). Use when the agent needs a fact before planning its next action.
Read the current state of a unit — current phase, status, shipped milestones, model timeline — or find units that match a predicate. Works for active, archived, abandoned, and handed-off units alike (projections are pure historical reads). Use when the agent needs a fact before planning its next action.
Record a gate decision with long-form rationale on the active unit. The canonical Knotch workflow ships gates G0..G4 (Scope / Clarify / Plan / Review / Drift) with an 8-char `min_rationale_chars` floor — too-short text rejects as `RationaleTooShort`. Adopter-forked workflows may expose different gate vocabularies.
Record a phase completion or skip on the active unit. The canonical `Knotch` workflow phases are `specify → plan → build → review → ship`; adopter-forked workflows may expose different names — run `knotch show --format json` on the active unit to see the current vocabulary. Does NOT handle milestones (those attach to commits via a `Knotch-Milestone:` git trailer — see "When NOT to use").
| name | knotch-transition |
| description | Transition the active unit to a new lifecycle status. Use when declaring the unit shipped, archived, abandoned, handed-off, or deprecated. Terminal transitions require every required phase to be resolved, or a forced override with rationale. |
| argument-hint | <target-status> [--forced --reason <text>] |
| allowed-tools | Bash(knotch transition *) Bash(knotch current) |
Move the unit to a new status.
Canonical Knotch workflow vocabulary:
draft, in_progress, in_review, shipped — non-terminal,
always allowed.archived, abandoned, superseded, deprecated.Adopter-forked workflows may expose a different status set;
knotch transition warns when the target is outside
W::known_statuses() but proceeds (the kernel's StatusId is
open-universe).
knotch transition <target>
knotch transition <target> --forced --reason <rationale>
Examples:
knotch transition in_review
knotch transition archived --forced --reason "upstream feature dropped"
EventBody::StatusTransitioned { target, forced, rationale }.
knotch current — confirm the active unit and its current status.NoOpStatusTransition.W::required_phases(scope) must be completed or skipped
(Phase × Status cross-invariant — see
@.claude/rules/preconditions.md).--reason is mandatory. Without it, the
precondition fails with ForcedWithoutRationale.git commit plus the
verify-commit hook./knotch-mark.knotch supersede <event-id>.