Loading...
Loading...
Found 11 Skills
File or link CawPlan defects from failed/blocked TestRail Results via QA Insights A4. Use when: SQA wants to turn a TestRail Failed/Blocked Result into a CawPlan Ticket, paste a tests/view URL to file a defect, review an A4 defect draft, create a BUGFIX/FEATURE ticket, or link an existing ticket back to TestRail defects. Cold start with tests/view MUST call execution failures --test-id BEFORE defects draft; never use test_id as the draft path result_id. A4 write path (create-ticket) MUST use --body-file or --body JSON — never field flags like --description or --result-id. NOT for: importing test cases (use `cawplan-testcase-import`); creating TestRail Plans/Runs (use `cawplan-testplan-layout`); release risk assessment; generating requirements or test points.
Query and summarize CawPlan QA Insights A3 TestRail execution progress for a Version or Run: execution rate, pass quality, deduplicated failure/blocker queue, and per-Ticket progress tables. Use when: A3 execution progress, test execution summary, TestRail run progress, execution summary, failure list, pass rate, untested count, status counts, custom status, 查询A3执行进度、查询Version测试进度、查询TestRail Run进度、执行摘要、失败列表、通过率、未执行统计、全status统计。 NOT for: importing test cases, creating TestRail Plans/Runs, filing defects (use `cawplan-defect-ticket`), or release risk assessment.
Orchestrate CawPlan QA Insights TestRail test plans from Version/Ticket-scoped imported cases with preview-first workflow. Use when: creating or executing A2 TestRail Plans/Runs for a CawPlan version or one or more CawPlan tickets after cases have been imported. NOT for: importing test cases (use `cawplan-testcase-import`); generating test points; execution summaries; defect filing; release risk. Do NOT use `cawplan api GET /api/v1/public/openapi/product/{product_id}` to resolve product name — that route does not exist.
Query one or more CawPlan tickets and show their current details in the conversation. Use when: the user gives or mentions CawPlan issue URLs, display IDs, or ticket unique IDs and wants ticket context. Automatically run when a CawPlan issue URL appears with no other workflow intent, even if the user did not explicitly ask to query ticket context. NOT for: creating tickets, updating tickets, downloading or adding attachments (use cawplan-ticket-attachments), product status reporting, codebase exploration, implementation, file edits, or SQA requirement analysis.
Aggregate CawPlan product insights: user feedback and critical issues. Use when: the user asks for a product health overview, user feedback trends, or a combined product insights summary. NOT for: date-range activity reports, ticket creation, single-metric queries, user activity, or device/app adoption metrics (installations, crash rate -- that public endpoint has been retired, no longer available via CLI).
Prepare, validate, import, reconcile, and correct Support Ops daily ticket metrics from Google Sheets or exported JSON into CawPlan's cawplan_csm key-metrics domain. Use when: Support asks to onboard its ticket dashboard data, backfill or upload Support ticket counts, validate a Support metrics export, compare CawPlan metrics with the Support sheet, or generate a safe Apps Script exporter. NOT for: generic CawPlan business metrics, device/app telemetry, editing the Support dashboard UI, producing the weekly Google Doc, or inventing new CSM metric names and tags.
Manually link existing TestRail Cases or Plans/Runs back to CawPlan mappings after QA hand-imported or hand-created TestRail artifacts. Link matches requirement_id + test_point_id in refs only (no hash validation). Use when: linking CSV-imported cases by refs; binding hand-made TestPlan/TestRun to CawPlan tickets; 用例回链、refs 映射、Plan Run 绑定、手工导入后 link. Ideal path after A3 CSV import: auto Suite → AutoScan → one confirm. NOT for: creating TestRail cases (use `cawplan-testcase-import`); creating Plans/Runs (use `cawplan-testplan-layout`); generating/exporting cases (use `cawplan-testcase-generate`); execution progress or defect filing.
Expand archived test points into executable test cases: preview titles in Markdown first, expand steps on demand, and export a team CSV when SQA explicitly requests it after review (read-only; does not write to CawPlan). Use when: generating test cases (preview first), expanding executable steps in a Markdown preview, exporting CSV when SQA asks to export, or handling a hot handoff after A2 (for example, “generate test cases from the above” or similar); use a cold handoff via Test Suite Link, display_id, or requirement_id. NOT for: test-point coverage outlines (use `cawplan-testpoint-generate`); requirement analysis or archiving (use `cawplan-requirement-analyze`); viewing or editing archived test points in the Test Suites web UI; or unarchived five-field drafts only (archive via A1 first).
Track CawPlan release progress for a version: ticket completion, risk level, open items, target release dates, unresolved Critical-priority bugs, features not yet at QA Testing, what's Ready for QA/QA Testing, descope suggestions, what's blocking QA testing, assignee overload, per-QA pending counts, and tickets stale for more than N days. Use when: the user asks to track a release, check release progress, review open tickets for a version, assess release/delay risk, ask what to descope, ask what's Ready for QA / in QA Testing for a version, ask what's blocking QA testing, ask if any assignee has too many high-priority issues piled up, ask how many tickets each QA still has to verify, or ask which tickets haven't been fixed in over N days. NOT for: creating versions or tickets, product-wide metrics dashboards not scoped to a version, user activity summaries, or open-ended critical-issue search across products (use `cawplan critical search` directly for that).
Generate and upsert a Ticket-scoped QA Report (PROGRESS or COMPLETION) for any CawPlan Ticket (anchor) + Version: collect anchor-relative subtree/relation/execution data, apply result rules, render ticket-qa-report.1 template, and persist via existing Portal qa_report POST/PUT. Use when: SQA asks for a test progress or completion QA report for a ticket and version (Story, requirement sub-ticket, or BUGFIX); republish/update an existing linked report; include related/blocking tickets in report scope. NOT for: Version Quality Report or AQA automation rollup; release risk assessment (use A5 separately); importing cases (A1), plan layout (A2), or defect filing (A4). V1 zero-BE: Agent-side upsert; approximate coverage; anchor-relative subtree depth ≤ 3.
Create a CawPlan version plan: create a version and optionally populate it with tickets, either from an explicit ticket list or by extracting work items from pasted OKRs/stage goals — deduplicating against the existing backlog and adding a rough, clearly-labeled effort estimate. Use when: the user asks to create a version plan, set up a new release, create a version with goals or tasks, plan a release train, or pastes OKRs/quarterly goals and asks to turn them into a version plan. NOT for: tracking an existing plan, creating standalone backlog tickets outside of a new version plan, querying product info, or metrics.