Convex Component Adoption Planner

Use this skill when a private Convex app needs a serious answer to any of these:

Should we adopt a specific Convex component?
Which Convex component best fits a planned feature?
How should a component integrate without creating duplicate ownership?
Generate a fresh-session execution package for adopting or explicitly rejecting a component.

Core stance

Always inspect the app's current durable owner before recommending a component.
Prefer one canonical owner. If a component would create a second source of truth, recommend against it unless the plan is a full hard-cut replacement.
Keep deterministic prep in the helper CLI. Keep architecture, ownership, and recommendation judgment in the model.
Use live Convex docs first. If the user asks for the latest or current component state, fetch it.
Ask remaining design questions one at a time with request_user_input, and include weighted scores from 0.0 to 10.0 for each option.