CawPlan Plan Track

Bootstrap

cawplan skill check

Important CLI constraint — read before writing any ticket-fetch command

cawplan tickets search requires --time_range or --start_date+--end_date unless you're doing an exact --unique_ids/--display_ids/--parent_ids lookup — --version_ids/--product_ids/--priority/--type alone do not satisfy this and the command exits with an error before it even calls the API (see references/CAWPLAN_OPEN_API.md's "Canonical workaround for 'every matching ticket regardless of age' queries" — this skill picks that section's option 2). Release tracking needs tickets regardless of how long ago they were touched, so this skill does not use tickets search for version-wide ticket lists — it uses tickets poll instead, which has no time window at all. tickets poll in turn does not accept --version_ids (only --product_ids/--product_line_ids) — filter down to the target version client-side from its response's version_id field. Don't reintroduce a bare tickets search --version_ids ... call anywhere in this skill; it will fail.

Workflow

Required product-access gate

Before querying any product-, version-, release-, or ticket-scoped data, verify that the caller can see the product through products list. This applies even when the user supplied a product_id directly or it came from an earlier conversation — never treat a known ID as proof of access.