DigitalConsumer.FixMyGlass/.cursor/skills/testing-skill/SKILL.md

name	description
testing-skill	Create Jira test cards using the Testing Skill workflow. When the user asks to create cards using Testing Skill, testing skill, or /testing-skill. Cards use Background: and Scope of Change: description format, default parent epic CONT-905, and System Analyst Scott Phillips. Use for test card creation on the CONT board with standardized fields.

Testing Skill

Keywords

testing skill, testing skill card, create test card, /testing-skill, use testing skill, test jira card

Overview

Create Jira cards using a standardized Testing Skill workflow with fixed defaults for test and demo card creation.

Use this skill when: The user explicitly asks to create cards using Testing Skill (or /testing-skill).

Do NOT use for: General Jira card creation → use create-jira-card instead.

---

Fixed Defaults

Apply these defaults on every card unless the user explicitly overrides them in the same request:

Field	Default value
Project	CONT
Issue type	Story
Parent epic	CONT-905
System Analyst	Scott Phillips

System Analyst lookup

Resolve Scott Phillips once per session:

lookupJiraAccountId(
  cloudId="...",
  searchString="Scott Phillips"
)

Use account ID 557058:6c212fb7-af94-48db-91a9-99ba87ceb3c5 if lookup succeeds with Scott Phillips (scott.phillips@safelite.com).

Set via additional_fields:

{
  "customfield_10008": "CONT-905",
  "customfield_14823": { "accountId": "557058:6c212fb7-af94-48db-91a9-99ba87ceb3c5" }
}

Also pass parent: "CONT-905" when creating the issue.

---

Description Format

CRITICAL: Every Testing Skill card description MUST use exactly these two labeled sections with trailing colons:

Background:
[Why this work exists or what problem it addresses]

Scope of Change:
[What will change]

Rules:

• Use Background: and Scope of Change: (capital C in Change)
• Each label on its own line, followed by content on the next line(s)
• Blank line between sections
• Do not use Description: in Testing Skill cards — only Background and Scope of Change

Example:

Background:
Add consent checkboxes when users provide email or phone numbers.

Scope of Change:
Add UI checkboxes per mocks (to be provided). Functionality handled in a separate card.

---

Workflow

1. Parse request — Extract summary/title and content for Background and Scope of Change
2. Draft card — Apply fixed defaults + formatted description
3. Confirm — Show draft to user before creating (unless user gave complete explicit details and said to create)
4. Create — Call createJiraIssue with defaults
5. Summarize — Return issue key and link

---

Create in Jira

createJiraIssue(
  cloudId="...",
  projectKey="CONT",
  issueTypeName="Story",
  summary="[Card title from user]",
  description="Background:\n[background]\n\nScope of Change:\n[scope]",
  parent="CONT-905",
  additional_fields={
    "customfield_10008": "CONT-905",
    "customfield_14823": { "accountId": "557058:6c212fb7-af94-48db-91a9-99ba87ceb3c5" }
  }
)

---

Confirmation Format

Here's the Testing Skill card I'll create:

**Project:** CONT
**Type:** Story
**Summary:** [title]
**Epic:** CONT-905
**System Analyst:** Scott Phillips

**Description:**
Background:
[background]

Scope of Change:
[scope]

Shall I create this card?

---

Overrides

Only change defaults if the user explicitly specifies otherwise in the same request:

• Different epic → use user's epic instead of CONT-905
• Different project → use user's project (still set epic link if provided)
• Different System Analyst → lookup and use specified person

If the user only provides a title, ask for Background and Scope of Change content before creating.

---

Quick Reference

Item	Value
Skill name	Testing Skill
Invoke	/testing-skill or "create using testing skill"
Project	CONT
Epic	CONT-905
System Analyst	Scott Phillips
Description sections	Background: + Scope of Change: