CawPlan Ticket Context

Bootstrap

cawplan skill check

Workflow

Ticket field semantics

For CawPlan tickets, description is the short title and remarks is the detailed page description/body (often HTML). Always label and present these fields accordingly; do not treat description as the body or omit remarks when showing ticket context.

Use this skill when the user invokes /cawplan-ticket-context, asks to query ticket context, or mentions a CawPlan issue URL in the session.

Automatically trigger this skill when the user message contains a CawPlan issue URL such as https://app.cawplan.com/issue/CWP-14471 or https://core-web-product.uid.dev.ui.com/issue/CAW-04560 and they are not asking for SQA requirement analysis, five-field structuring, module-tree selection, or QA Insights archiving — use cawplan-requirement-analyze for those. Do not wait for an explicit /cawplan-ticket-context command when only a bare issue URL is pasted.

This skill is display-only. After looking up and showing the ticket details, stop. Do not inspect the repository, search source files, infer an implementation plan, run tests, edit files, commit changes, or continue into another workflow unless the user explicitly asks for that follow-up work.