knock-migrate-to-knock
Migrate to Knock skill
Discover the current messaging stack in this codebase, map it to Knock concepts, and produce an ordered migration plan. This is a discovery and recommendation skill.
Hard constraint
Do not create, update, push, commit, or delete Knock resources (workflows, guides, users, tenants, preferences, partials, layouts) via MCP or CLI unless the user explicitly asks after reviewing the plan. Do not run production imports. Output plans, inventories, and optional local app-code suggestions only.
Output contract (hard)
Write the inventory and migration plan to knock-plan.md at the repo root (the shared plan file used by knock-product-messaging-strategy and knock-lifecycle-opportunities; create or update — do not create a second plan). Keep chat minimal — status + confirmation only.
Do not paste the inventory table or the full phased plan into chat.
Allowed chat content:
- One short status line (path + counts, e.g. platforms detected and message types found)
- Optional one-line blocker
- Bold confirmation question as the last line