Terminal
Terminal/Skill
Scans a product codebase for activation, engagement and retention moments, and recommends lifecycle messages without creating Knock resources.
By Knock
Works with
npx skills add knocklabs/skills --skill knock-lifecycle-opportunitiesFind 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.
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.
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:
Example:
Wrote knock-plan.md with 6 ranked opportunities.
Which opportunities should we take next?
rules/map-product-lifecycle.md) — write signals into the filerules/select-opportunities.md) — rank in the filerules/opportunity-brief-format.md) — full briefs in the file onlyknock-plan.md.### Setup handoff
- **plan.** knock-plan.md
- **confirmed.** [names or indexes]
- **skipped.** [names or indexes]
- **deferred / blocked.** [names + reason]
knock-setup must treat confirmed as authoritative, read detail from knock-plan.md, and skip rediscovery. For fuller strategy design, hand off confirmed items to knock-product-messaging-strategy (same knock-plan.md).
rules/map-product-lifecycle.md — where to look in coderules/select-opportunities.md — prioritizationrules/opportunity-brief-format.md — plan file structure and chat brevity