CawPlan Product Insights
Bootstrap
cawplan skill check
Workflow
Resolve product name to
product_id:cawplan products list --search "<product name>"Continue only after one exact accessible product-name match (case-insensitive after trimming whitespace), one unique short-form/token-prefix match, or an explicit user confirmation of a candidate. If the user's stated product is absent or ambiguous, list the candidates and ask which product they mean; never silently choose a non-unique similarly named product. Do not fetch insight sources until the product is confirmed. Report
NO_PERMISSIONonly for an explicit access-denied response.Fetch all insight sources in parallel:
Adoption & health metrics (installations, crash rate, offline rate):
cawplan metrics get <product_id> --time_range 1m # or with explicit dates: cawplan metrics get <product_id> --start YYYY-MM-DD --end YYYY-MM-DDAI feedback analytics (feedback categories and trends):
cawplan analytics get <product_id> --time_range 1mCritical issues (active blockers and incidents):
cawplan critical list <product_id>
Output
Structure the insights as:
- Adoption: install base, active devices, growth trend.
- Stability: crash rate, offline rate, notable anomalies.
- User feedback: top feedback categories, notable shifts.
- Critical issues: count and severity of active blockers.
- Key takeaways: 2–3 bullet points on what needs attention.
Highlight notable shifts or outliers. Avoid overstating causality.
Decision Guide
- For a specific metric trend only: use
/cawplan-metrics. - For feedback categories only: use
/cawplan-analytics. - For date-range activity report: use
/cawplan-product-report.
References
references/CAWPLAN_OPEN_API.md