Workflow migration

Kin has retired its scripted workflow runtime. Recurring procedures now use skills in the ordinary conversation, with subagents when delegation helps.

The commands you can keep using

/critique, /security-review, /revise, /research, and /deep-research remain available. They now send instructions through a normal turn, so their answers remain available for follow-up and session resume. They also work with headless skill invocation, such as kin -p "/research explain the parser".

These skills scale the work to your question. They can use a focused child for independent review or investigation, without requiring a fixed panel, sequence of phases, or repeated scoring. Delegated children use the ordinary agent panel, retained output, steering, and lifecycle controls. Tools follow your session’s normal permission policy.

The standalone cite_check tool remains available. The deep-research skill instructs Kin to check its final citations and disclose any verification failure.

Convert a saved script

The workflow tool, /workflow, /workflow-save, and /workflows panel have been removed. A saved kind: workflow skill is invalid and reports a migration diagnostic. Its name still shadows lower-priority copies, so an old project override cannot silently invoke a different bundled skill.

Open the bundle through /config → skill, or use /skill-creator to rewrite the procedure. Replace the Python body with instructions describing the goal, useful evidence, and expected result. Then use kind: prompt (or omit kind, which defaults to prompt). Changing only the kind leaves Python where instructions should be and is not a migration.

For example, a reusable review can be expressed as:

---
name: review-branch
description: Review the requested branch changes for concrete defects.
kind: prompt
disable-model-invocation: true
---
Review $ARGUMENTS. Read the relevant diff and surrounding code. Use an
independent reviewer when it helps resolve a specific uncertainty. Report
supported defects with their location, failure case, and proposed correction.
If no actionable defect is found, say so.

Keep deterministic project automation in ordinary workspace scripts where that is useful. Kin can invoke them through its existing tools and permission policy; a skill does not grant new authority.

Existing state

Kin leaves saved skill files, artifacts, worktrees, and session journals on disk. Historical workflow tool results remain readable in conversation replay. The old saved-run cache is no longer executable, and results that older saved workflows never placed in history cannot be reconstructed automatically.

Old model_assignments.workflow entries and "workflow" placement in selectable_for are inert. They do not grant task placement; choose a Tasks or profile assignment explicitly in /models if you want one. The workflow-first nudge is retired and ignored when an old session resumes. /nudges currently has no available preferences.