vaylo-qa-tools — Claude plugins for the QA team

Claude plugins for the QA team.

Plugin	What it does
weekly-deployment	Reads the weekly deployment Jira ticket's description (the source of truth), then updates that description and posts the deployment announcement to #prod-deploy-disc — grouped by QA, with real @mentions and clickable ticket links. Ships a skill (weekly-deployment-update) + an agent (deployment-reporter). Needs Jira + Slack connectors.
api-testing	Turns a Postman collection into pm.test scripts, test case tables, manual checklists, and defect reports — entirely inside Postman. No connectors needed, works standalone.

api-testing needs no org rollout or connector setup — install it (/plugin install api-testing@vaylo-qa-tools) and go. Everything below in this README (rollout plan, admin steps, connectors) is specific to weekly-deployment, which does need those.

---

Rollout plan — weekly-deployment

The goal is for every QA member to have this in Claude Code, Claude web chat, and Cowork. Each surface is enabled differently:

Surface	How it's enabled	Status
Claude Code (CLI / VS Code / Desktop "Code" tab)	Admin turns it on for the org (managed settings), or each person self-installs	✅ Ready now
Claude web chat (claude.ai)	Admin publishes the chat version as an Organization Skill	⏳ Needs the chat-skill/ (being built)
Cowork	Each person self-installs (org-wide isn't available yet)	✅ Works per-user now

Two people make this happen: a Claude org admin (turns it on for everyone) and each QA member (connects their own Jira + Slack the first time). Instructions for both are below.

---

For the Claude Org Admin

You are the only one who can turn this on for the whole company at once. Everything is in claude.ai → Admin settings (exact labels may vary slightly).

1. Claude Code — auto-install for everyone ✅ do this now

• Go to Admin settings → Claude Code → Managed settings.
• Add this (merge into any existing config), then Save:

  {
    "extraKnownMarketplaces": [
      { "source": "github", "repo": "strativ-dev/vaylo-qa-tools" }
    ],
    "enabledPlugins": [
      { "marketplace": "vaylo-qa-tools", "plugin": "weekly-deployment" }
    ]
  }

• It syncs to all members and installs on their next Claude Code launch.

2. Repo access ✅ do this now

• Make github.com/strativ-dev/vaylo-qa-tools readable by all org members (grant team access or make it internal). If they can't read it, the plugin won't load.

3. Connectors ✅ do this now

• Go to Admin settings → Connectors and enable Atlassian (Jira) and Slack for the org, so members can read tickets and post messages.

4. Claude web chat — the chat version ⏳ wait until chat-skill/ exists

• Go to Admin settings → Skills, upload + publish the skill from the repo's chat-skill/ folder, and enable it for all members.
• (This folder is being created — don't do this step until it's in the repo.)

5. Cowork

• Org-wide distribution isn't available yet. For now members self-install (see below). Once Anthropic ships org-wide Cowork support, the same managed-settings config covers it.

---

For QA Team Members

Get it

• Claude Code: If the admin has enabled it, it's already there — nothing to do. Otherwise install it once:

  /plugin marketplace add strativ-dev/vaylo-qa-tools
  /plugin install weekly-deployment@vaylo-qa-tools
  

  Doing API test work too? Add /plugin install api-testing@vaylo-qa-tools — no extra setup, no connectors needed.
• Cowork: run the same commands once inside Cowork.
• Claude web chat: nothing to install for weekly-deployment — once the admin publishes the chat skill, it shows up in your Skills panel automatically.

Connect your integrations (first time only)

In claude.ai → Settings → Connectors, connect:

1. Atlassian (Jira) — the vaylo.atlassian.net site, with access to the VAY project.
2. Slack — the Vaylo workspace; make sure you're a member of #prod-deploy-disc.

When you run it, the Slack message posts under your Slack identity.

Run it

Give Claude the weekly deployment ticket key. Either:

• Agent: Use deployment-reporter to process VAY-4522
• Skill: /weekly-deployment:weekly-deployment-update and give it the key.

What it does:

1. Reads that deployment ticket's live description — the tickets and QA/BE/FE people written there are the source of truth (it never invents or drops people).
2. Posts the announcement to #prod-deploy-disc with real @mentions and ticket links.
3. Reports back the ticket URL, the exact Slack text, and the message link.

Good to know

• A blank role shows as - (e.g. FE: - | BE: @Rakibul).
• It edits a real ticket and pings real people — check the ticket description is correct first.
• Trouble? Ping Minar (minar.rafi@strativ.se).

---

Maintenance

Each plugin's own README has its maintenance details (where to edit, how to bump versions, how to regenerate any build artifacts):

• plugins/weekly-deployment/README.md
• plugins/api-testing/README.md

The short version for any plugin: edit its skills/ (and agents/, if it has one), bump version in that plugin's .claude-plugin/plugin.json and the matching entry in the repo's root .claude-plugin/marketplace.json, commit, and push. Teammates pick it up on their next marketplace refresh (/plugin marketplace update vaylo-qa-tools).