Lifecycle opportunities skill

Find where users activate, stall, pay, invite, or churn in this product’s code and data model. Recommend messaging opportunities tied to real events and UI states.

Hard constraint

Do not create, update, push, or delete Knock resources via MCP or CLI. Output an opportunity backlog and event/trigger sketches only. Hand off to knock-setup or knock-product-messaging-strategy only if the user asks to build.

Output contract (hard)

Write all detailed findings to knock-plan.md at the repo root (create or update). Keep chat minimal — status + confirmation only.

Do not paste opportunity briefs, code-path inventories, or long rationale into chat. Follow rules/opportunity-brief-format.md.

Allowed chat content:

1. One short status line (path + count)
2. Optional one-line blocker
3. Bold confirmation question as the last line