Refine ticket

Skill Diegocortes15/playwright-ia-automation-framework-saucedemo/.claude/skills/refine-ticket

An end-to-end test framework where a Jira ticket becomes a reviewed, TCMS-mirrored Playwright pull request — authored by AI agents, gated by deterministic CI. Built on saucedemo as both a reusable template and a portfolio piece.

Install

npx -y skills add Diegocortes15/playwright-ia-automation-framework-saucedemo --skill refine-ticket

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Iteratively harden a Jira automation ticket against a "bulletproof" rubric — grounded in existing automation, app docs, and user-supplied sources — then write the refined acceptance criteria back to the ticket on approval, so /from-issue has nothing left to guess.

SKILL.md

3.1 KB, as published. Nobody here has run it

refine-ticket

Given a Jira issue key (e.g. SW-123), this skill reads the ticket via the Atlassian MCP, scores it against the refinement rubric, and loops — auto-resolving gaps from existing automation + docs and asking you (or a source you point it at) for the rest — until the ticket is unambiguous. On your approval it writes a ## Refined Acceptance Criteria block back to the ticket. It does NOT generate tests; run /from-issue after. See ADR-0013.

How to use it

Tell Claude what you want:

Use the refine-ticket skill on SW-123.

Or to preview without writing to Jira:

Use the refine-ticket skill on SW-123 with dry-run.

During the loop, when asked about a gap you can either answer directly or point the skill at a source ("it's in Confluence page X", a URL, a doc path). The skill ingests it and continues. It does NOT inspect a running app — it's shift-left, so it works even before the feature is built. It stops when the ticket has no open gaps, then asks before writing anything back.

Workflow

The full procedural workflow is in references/workflow.md. Read that file before executing the skill.

Setup note: the Atlassian MCP must be connected (OAuth) with write scope for the Step 7 description update — defined at project scope in .mcp.json. Its read + write tools are pre-authorized in allowed-tools above so the loop doesn't prompt each call. Write-back happens only on your explicit approval (per ADR-0013).

References

references/workflow.md — the procedural loop
references/rubric.md — the "bulletproof" checklist (definition of done)
references/sources.md — source catalog + user-supplied-source protocol
references/writeback-template.md — the ## Refined Acceptance Criteria block + idempotent-update rule

Composition

This skill pairs with /from-issue: refine first, then generate. It reuses /from-issue's bucket-classification.md and qa-analysis.md for the rubric's coverage/automatable judgment.