Agent skill

Qcsd Production Swarm

by proffesor-for-testing in proffesor-for-testing/agentic-qe

A skill your agent uses when assessing post-release production health with DORA metrics, root cause analysis, defect prediction, or cross-phase feedback loops in the QCSD Production phase.

MITAuto-check passedDevelopment

Install Qcsd Production Swarm

skills CLI
$ npx skills add proffesor-for-testing/agentic-qe --skill qcsd-production-swarm -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install proffesor-for-testing/agentic-qe qcsd-production-swarm --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/qcsd-production-swarm .claude/skills/qcsd-production-swarm && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
qcsd-production-swarm
GitHub stars
495
Token cost
~2.3k tokens
SKILL.md length
726 words
Files
13 (incl. scripts)
Skills in repo
93
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when assessing post-release production health with DORA metrics, root cause analysis, defect prediction, or cross-phase feedback loops in the QCSD Production phase.

  • Works in 9 steps: Flag Detection --… → Core Agents -- steps/02-core-agents.md… → Batch 1 Results --… → …
  • Assessing post-release production health with DORA metrics
  • SKILL.md covers Overview, ENFORCEMENT RULES - READ FIRST, Step Execution Protocol and Agent Inventory, plus 4 more sections
  • Root cause analysis

What it does

Qcsd Production Swarm is an agent skill from proffesor-for-testing/agentic-qe. Use when assessing post-release production health with DORA metrics, root cause analysis, defect prediction, or cross-phase feedback loops in the QCSD Production phase.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including scripts (for example `evals/qcsd-production-swarm.yaml`, `schemas/output.json` and `scripts/validate-config.json`).

It sits in Development, covering Root cause analysis. The repository describes itself as: Agentic QE Fleet is an open-source AI-powered QA/QE platform designed for use with Coding Agents (works best with Claude Code) featuring specialized agents and skills to support… The licence is MIT.

When your agent uses it

  • Assessing post-release production health with DORA metrics
  • Root cause analysis
  • Defect prediction
  • Cross-phase feedback loops in the QCSD Production phase

Example prompts

  • “/qcsd-production-swarm”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Flag Detection -- steps/01-flag-detection.md -- Retrieve CI/CD signals, detect telemetry source, evaluate all 7 flags
  2. Core Agents -- steps/02-core-agents.md -- Spawn qe-metrics-optimizer, qe-defect-predictor, qe-root-cause-analyzer in parallel
  3. Batch 1 Results -- steps/03-batch1-results.md -- Wait for core agents, extract all metrics
  4. Conditional Agents -- steps/04-conditional-agents.md -- Spawn flagged conditional agents in parallel
  5. Decision Synthesis -- steps/05-decision-synthesis.md -- Apply HEALTHY/DEGRADED/CRITICAL logic
  6. Report Generation -- steps/06-report-generation.md -- Generate executive summary and full report
  7. Learning Persistence -- steps/07-learning-persistence.md -- Store findings to memory, save persistence record
  8. Feedback Loop -- steps/08-feedback-loop.md -- Run learning coordinator then transfer specialist (sequential)
  9. Final Output -- steps/09-final-output.md -- Display completion summary with all scores

What it can do on your machine

Read from SKILL.md and the folder at commit 1363bc7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Qcsd Production Swarm loads about 2.3k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 726 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from proffesor-for-testing/agentic-qe at commit 1363bc7, republished under its MIT licence (© proffesor-for-testing). 726 words, ~2,281 tokens.

Download SKILL.mdSave it as .claude/skills/qcsd-production-swarm/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
qcsd-production-swarm
description
Use when assessing post-release production health with DORA metrics, root cause analysis, defect prediction, or cross-phase feedback loops in the QCSD Production phase.
category
qcsd-phases
priority
critical
version
1.0.0
tokenEstimate
32000
agents.core
qe-metrics-optimizer, qe-defect-predictor, qe-root-cause-analyzer
agents.conditional
qe-chaos-engineer, qe-performance-tester, qe-regression-analyzer, qe-pattern-learner, qe-middleware-validator, qe-sap-rfc-tester, qe-sod-analyzer
agents.feedback
qe-learning-coordinator, qe-transfer-specialist
agents.total
12
agents.sub_agents
0
skills
shift-right-testing, chaos-engineering-resilience, quality-metrics, performance-testing, holistic-testing-pact

QCSD Production Swarm v1.0

Post-release production health assessment and QCSD feedback loop closure.


Overview

The Production Swarm assesses release health in the live production environment using DORA metrics, incident RCA, defect prediction, and cross-phase feedback loops. It renders a HEALTHY / DEGRADED / CRITICAL decision and is the only QCSD phase with dual responsibility: assessing current production health AND closing the feedback loop back to Ideation and Refinement phases.

QCSD Phase Positioning
PhaseSwarmDecisionWhen
Ideationqcsd-ideation-swarmGO / CONDITIONAL / NO-GOPI/Sprint Planning
Refinementqcsd-refinement-swarmREADY / CONDITIONAL / NOT-READYSprint Refinement
Developmentqcsd-development-swarmSHIP / CONDITIONAL / HOLDDuring Sprint
Verificationqcsd-cicd-swarmRELEASE / REMEDIATE / BLOCKPre-Release / CI-CD
Productionqcsd-production-swarmHEALTHY / DEGRADED / CRITICALPost-Release
Parameters
  • TELEMETRY_DATA: Path to production telemetry, incident reports, and DORA metrics (required)
  • RELEASE_ID: Release identifier for tracking (optional)
  • OUTPUT_FOLDER: Where to save reports (default: ${PROJECT_ROOT}/Agentic QCSD/production/)
  • SLA_DEFINITIONS: Path to SLA/SLO target definitions (optional)

ENFORCEMENT RULES - READ FIRST

RuleEnforcement
E1You MUST spawn ALL THREE core agents in Step 2. No exceptions.
E2You MUST put all parallel Task calls in a SINGLE message.
E3You MUST STOP and WAIT after each batch. No proceeding early.
E4You MUST spawn conditional agents if flags are TRUE. No skipping.
E5You MUST apply HEALTHY/DEGRADED/CRITICAL logic exactly as specified in Step 5.
E6You MUST generate the full report structure. No abbreviated versions.
E7Each agent MUST read its reference files before analysis.
E8You MUST run BOTH feedback agents in Step 8 SEQUENTIALLY. Always. Both agents.
E9You MUST execute Step 7 learning persistence. No skipping.

PROHIBITED BEHAVIORS:

  • Summarizing instead of spawning agents
  • Skipping agents "for brevity"
  • Proceeding before background tasks complete
  • Providing your own analysis instead of spawning specialists
  • Omitting report sections or using placeholder text

Step Execution Protocol

This skill uses a micro-file step architecture. Each step is a self-contained file loaded one at a time to avoid "lost in the middle" context degradation.

Execute steps sequentially by reading each step file with the Read tool.

Steps
  1. Flag Detection -- steps/01-flag-detection.md -- Retrieve CI/CD signals, detect telemetry source, evaluate all 7 flags
  2. Core Agents -- steps/02-core-agents.md -- Spawn qe-metrics-optimizer, qe-defect-predictor, qe-root-cause-analyzer in parallel
  3. Batch 1 Results -- steps/03-batch1-results.md -- Wait for core agents, extract all metrics
  4. Conditional Agents -- steps/04-conditional-agents.md -- Spawn flagged conditional agents in parallel
  5. Decision Synthesis -- steps/05-decision-synthesis.md -- Apply HEALTHY/DEGRADED/CRITICAL logic
  6. Report Generation -- steps/06-report-generation.md -- Generate executive summary and full report
  7. Learning Persistence -- steps/07-learning-persistence.md -- Store findings to memory, save persistence record
  8. Feedback Loop -- steps/08-feedback-loop.md -- Run learning coordinator then transfer specialist (sequential)
  9. Final Output -- steps/09-final-output.md -- Display completion summary with all scores
Show full SKILL.md (305 more words)Show less
Execution Instructions
  1. Use the Read tool to load the current step file (e.g., Read({ file_path: ".claude/skills/qcsd-production-swarm/steps/01-flag-detection.md" }))
  2. Execute the step's instructions completely
  3. Verify all success criteria are met before proceeding
  4. Pass the step's output as context to the next step
  5. If a step fails, halt and report the failure point -- do not skip ahead
Resume Support

To resume from a specific step: specify --from-step N and the orchestrator will skip to step N. Ensure you have the required prerequisite data from prior steps.


Agent Inventory

AgentTypeDomainBatch
qe-metrics-optimizerCore (always)learning-optimization1
qe-defect-predictorCore (always)defect-intelligence1
qe-root-cause-analyzerCore (always)defect-intelligence1
qe-chaos-engineerConditional (HAS_INFRASTRUCTURE_CHANGE)chaos-resilience2
qe-performance-testerConditional (HAS_PERFORMANCE_SLA)chaos-resilience2
qe-regression-analyzerConditional (HAS_REGRESSION_RISK)defect-intelligence2
qe-pattern-learnerConditional (HAS_RECURRING_INCIDENTS)defect-intelligence2
qe-middleware-validatorConditional (HAS_MIDDLEWARE)enterprise-integration2
qe-sap-rfc-testerConditional (HAS_SAP_INTEGRATION)enterprise-integration2
qe-sod-analyzerConditional (HAS_AUTHORIZATION)enterprise-integration2
qe-learning-coordinatorFeedback (always, sequential)learning-optimization3
qe-transfer-specialistFeedback (always, sequential)learning-optimization3

Total: 12 agents (3 core + 7 conditional + 2 feedback)


Quality Gate Thresholds

MetricHEALTHYDEGRADEDCRITICAL
DORA Score>= 0.70.4 - 0.69< 0.4
SLA Compliance>= 99%95 - 98.9%< 95%
Incident SeverityP3/P4/NONEP2P0/P1
Defect Trenddeclining/stablestable (density > 2)increasing + density > 5
RCA Completeness>= 80%50 - 79%< 50%

Report Filename Mapping

AgentReport FilenameStep
qe-metrics-optimizer02-dora-metrics.md2
qe-defect-predictor03-defect-prediction.md2
qe-root-cause-analyzer04-root-cause-analysis.md2
qe-chaos-engineer05-chaos-resilience.md4
qe-performance-tester06-performance-sla.md4
qe-regression-analyzer07-regression-analysis.md4
qe-pattern-learner08-pattern-analysis.md4
Learning Persistence09-learning-persistence.json7
qe-middleware-validator10-middleware-health.md4
qe-sap-rfc-tester11-sap-health.md4
qe-sod-analyzer12-sod-compliance.md4
Feedback agents13-feedback-loops.md8
Synthesis01-executive-summary.md6

Execution Model Options

ModelWhen to UseAgent Spawn
Task Tool (PRIMARY)Claude Code sessionsTask({ subagent_type, run_in_background: true })
MCP ToolsMCP server availablefleet_init({}) / task_submit({})
CLITerminal/scriptsswarm init / agent spawn

Key Principle

Production health is measured by outcomes, not intentions. This swarm provides evidence-based production assessment and closes the QCSD feedback loop.

© proffesor-for-testing, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 12 other files (scripts) in assets/skills/qcsd-production-swarm of proffesor-for-testing/agentic-qe.

  • SKILL.md
  • evals/qcsd-production-swarm.yaml
  • schemas/output.json
  • scripts/validate-config.json
  • steps/01-flag-detection.md
  • steps/02-core-agents.md
  • steps/03-batch1-results.md
  • steps/04-conditional-agents.md
  • steps/05-decision-synthesis.md
  • steps/06-report-generation.md
  • steps/07-learning-persistence.md
  • steps/08-feedback-loop.md
  • steps/09-final-output.md

Open the folder on GitHubat commit 1363bc7

Compare with similar skills

Qcsd Production Swarm next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Qcsd Production Swarm compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qcsd Production Swarm this skillproffesor-for-testing/agentic-qe495—~2.3kAutomated safety check: PassMIT
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Review PRapache/shardingsphere21k—~6.5kAutomated safety check: PassApache-2.0
Graph-Based Bug Tracingtirth8205/code-review-graph32k1 repos~287Automated safety check: PassMIT

Similar skills

  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes
  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Review PR

    apache/shardingsphere

    Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.

    21k GitHub stars~6.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed
  • Om Auto Fix Issue

    go-musicfox/go-musicfox

    Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain…

    2.6k GitHub starsUsed in 1 repo~5k tokens
    DevelopmentAuto-check: notes

More from proffesor-for-testing/agentic-qe

All 93 skills in this repo
  • Contract Testing

    proffesor-for-testing/agentic-qe

    Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing.

    495 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Mutation Testing

    proffesor-for-testing/agentic-qe

    Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.

    495 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Performance Testing

    proffesor-for-testing/agentic-qe

    Profiles application performance under load using k6, Artillery, or JMeter to measure latency, throughput, and error rates.

    495 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Code Review Quality

    proffesor-for-testing/agentic-qe

    Conduct context-driven code reviews focusing on quality, testability, and maintainability.

    495 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Security Testing

    proffesor-for-testing/agentic-qe

    Scans for security vulnerabilities including XSS, SQL injection, CSRF, and auth flaws using OWASP Top 10 methodology.

    495 GitHub stars~2.7k tokensUpdated today
    Auto-check: notes
  • Database Testing

    proffesor-for-testing/agentic-qe

    Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.

    495 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Categories

Questions about Qcsd Production Swarm

What does Qcsd Production Swarm do?

A skill your agent uses when assessing post-release production health with DORA metrics, root cause analysis, defect prediction, or cross-phase feedback loops in the QCSD Production phase. Qcsd Production Swarm is an agent skill from proffesor-for-testing/agentic-qe. Use when assessing post-release production health with DORA metrics, root cause analysis, defect prediction, or cross-phase feedback loops in the QCSD Production phase.

When should I use Qcsd Production Swarm?

Qcsd Production Swarm fits situations like: assessing post-release production health with DORA metrics; root cause analysis; defect prediction; cross-phase feedback loops in the QCSD Production phase.

How do I install Qcsd Production Swarm in Claude Code?

Run `npx skills add proffesor-for-testing/agentic-qe --skill qcsd-production-swarm -a claude-code`. Or copy the skill folder (assets/skills/qcsd-production-swarm in proffesor-for-testing/agentic-qe) into .claude/skills/qcsd-production-swarm in your project. Claude Code loads it when a task matches its description.

How do I install Qcsd Production Swarm in Codex?

Run `npx skills add proffesor-for-testing/agentic-qe --skill qcsd-production-swarm -a codex`. Or copy the skill folder (assets/skills/qcsd-production-swarm in proffesor-for-testing/agentic-qe) into .agents/skills/qcsd-production-swarm in your project. Codex loads it when a task matches its description.

Can I use Qcsd Production Swarm in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add proffesor-for-testing/agentic-qe --skill qcsd-production-swarm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qcsd-production-swarm, .gemini/skills/qcsd-production-swarm, .github/skills/qcsd-production-swarm and .opencode/skills/qcsd-production-swarm in your project.

What does Qcsd Production Swarm need to run?

SKILL.md names no scripts, command-line tools or credentials: Qcsd Production Swarm is instructions for the agent only.

Does Qcsd Production Swarm access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Qcsd Production Swarm safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Qcsd Production Swarm use?

Qcsd Production Swarm is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qcsd Production Swarm use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Qcsd Production Swarm?

Skills that share tags, products or a category with Qcsd Production Swarm: OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Review PR (apache/shardingsphere, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qcsd Production Swarm?

proffesor-for-testing (a GitHub user) maintains it in proffesor-for-testing/agentic-qe, which has 495 GitHub stars. The repository holds 93 skills in this directory. The repository was last updated on October 9, 2026.

Source: proffesor-for-testing/agentic-qe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.