Agent skill

Qcsd Development Swarm

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

A skill your agent uses when monitoring in-sprint code quality with TDD adherence checks, complexity analysis, coverage gap detection, or defect prediction in the QCSD Development phase.

MITAuto-check passedTesting & QA

Install Qcsd Development Swarm

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

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

GitHub CLI
$ gh skill install proffesor-for-testing/agentic-qe qcsd-development-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-development-swarm .claude/skills/qcsd-development-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-development-swarm
GitHub stars
494
Token cost
~2.5k tokens
SKILL.md length
857 words
Files
13 (incl. scripts)
Skills in repo
95
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when monitoring in-sprint code quality with TDD adherence checks, complexity analysis, coverage gap detection, or defect prediction in the QCSD Development phase.

  • Works in 9 steps: Flag Detection --… → Core Agents -- steps/02-core-agents.md… → Batch 1 Results --… → …
  • Monitoring in-sprint code quality with TDD adherence checks
  • SKILL.md covers Overview, ENFORCEMENT RULES - READ FIRST, Step Execution Protocol and Agent Inventory, plus 4 more sections
  • Complexity analysis

What it does

Qcsd Development Swarm is an agent skill from proffesor-for-testing/agentic-qe. Use when monitoring in-sprint code quality with TDD adherence checks, complexity analysis, coverage gap detection, or defect prediction in the QCSD Development phase.

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

It sits in Testing & QA, covering Code quality, Test coverage and Test-driven development. 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

  • Monitoring in-sprint code quality with TDD adherence checks
  • Complexity analysis
  • Coverage gap detection
  • Defect prediction in the QCSD Development phase

Example prompts

  • “/qcsd-development-swarm”

Workflow steps

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

  1. Flag Detection -- steps/01-flag-detection.md -- Scan source code and tests, detect all 6 flags
  2. Core Agents -- steps/02-core-agents.md -- Spawn qe-tdd-specialist, qe-code-complexity, qe-coverage-specialist 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 SHIP/CONDITIONAL/HOLD 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. Defect Predictor -- steps/08-defect-predictor.md -- Run qe-defect-predictor analysis on all code changes
  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 829d030. 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 Development Swarm loads about 2.5k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 857 words of instructions outside code blocks.

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

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 829d030, republished under its MIT licence (© proffesor-for-testing). 857 words, ~2,527 tokens.

Download SKILL.mdSave it as .claude/skills/qcsd-development-swarm/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
qcsd-development-swarm
description
Use when monitoring in-sprint code quality with TDD adherence checks, complexity analysis, coverage gap detection, or defect prediction in the QCSD Development phase.
category
qcsd-phases
priority
critical
version
1.1.0
tokenEstimate
3400
agents.core
qe-tdd-specialist, qe-code-complexity, qe-coverage-specialist
agents.conditional
qe-security-scanner, qe-performance-tester, qe-mutation-tester, qe-message-broker-tester, qe-sap-idoc-tester, qe-sod-analyzer
agents.analysis
qe-defect-predictor
agents.total
10
agents.sub_agents
0
skills
tdd-london-chicago, mutation-testing, performance-testing, security-testing

QCSD Development Swarm v1.0

Shift-left quality engineering swarm for in-sprint code quality assurance.


Overview

The Development Swarm takes refined stories (that passed Refinement) and validates code quality during sprint execution. Where the Ideation Swarm asks "Should we build this?" and the Refinement Swarm asks "How should we test this?", the Development Swarm asks "Is the code quality sufficient to ship?"

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
  • SOURCE_PATH: Source code directory to analyze (required, e.g., src/auth/)
  • TEST_PATH: Test directory for coverage analysis (optional, e.g., tests/auth/)
  • OUTPUT_FOLDER: Where to save reports (default: ${PROJECT_ROOT}/Agentic QCSD/development/)

ENFORCEMENT RULES - READ FIRST

RuleEnforcement
E1You MUST spawn ALL THREE core agents (qe-tdd-specialist, qe-code-complexity, qe-coverage-specialist) 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 SHIP/CONDITIONAL/HOLD 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 apply qe-defect-predictor analysis on ALL code changes in Step 8. Always.
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 -- Scan source code and tests, detect all 6 flags
  2. Core Agents -- steps/02-core-agents.md -- Spawn qe-tdd-specialist, qe-code-complexity, qe-coverage-specialist 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 SHIP/CONDITIONAL/HOLD 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. Defect Predictor -- steps/08-defect-predictor.md -- Run qe-defect-predictor analysis on all code changes
  9. Final Output -- steps/09-final-output.md -- Display completion summary with all scores
Execution Instructions
  1. Use the Read tool to load the current step file (e.g., Read({ file_path: ".claude/skills/qcsd-development-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.


Show full SKILL.md (360 more words)Show less

Agent Inventory

AgentTypeDomainBatch
qe-tdd-specialistCore (always)test-generation1
qe-code-complexityCore (always)code-intelligence1
qe-coverage-specialistCore (always)coverage-analysis1
qe-security-scannerConditional (HAS_SECURITY_CODE)security-compliance2
qe-performance-testerConditional (HAS_PERFORMANCE_CODE)chaos-resilience2
qe-mutation-testerConditional (HAS_CRITICAL_CODE)test-generation2
qe-message-broker-testerConditional (HAS_MIDDLEWARE)enterprise-integration2
qe-sap-idoc-testerConditional (HAS_SAP_INTEGRATION)enterprise-integration2
qe-sod-analyzerConditional (HAS_AUTHORIZATION)enterprise-integration2
qe-defect-predictorAnalysis (always)defect-intelligence3

Total: 10 agents (3 core + 6 conditional + 1 analysis)


Quality Gate Thresholds

MetricSHIPCONDITIONALHOLD
TDD Adherence>= 80%60 - 79%< 60%
Code ComplexityAvg <= 10Avg 11-15Avg > 15
Test Coverage>= 80%60 - 79%< 60%
Mutation Score>= 70%50 - 69%< 50%
Security IssuesNo HIGH/CRITICALMEDIUM onlyHIGH/CRITICAL found

Report Filename Mapping

AgentReport FilenameStep
qe-tdd-specialist02-tdd-analysis.md2
qe-code-complexity03-complexity-analysis.md2
qe-coverage-specialist04-coverage-analysis.md2
qe-security-scanner05-security-scan.md4
qe-performance-tester06-performance-analysis.md4
qe-mutation-tester07-mutation-testing.md4
qe-message-broker-tester08-middleware-health.md4
qe-sap-idoc-tester09-sap-integration.md4
qe-sod-analyzer10-sod-compliance.md4
Learning Persistence11-learning-persistence.json7
qe-defect-predictor12-defect-prediction.md8
Synthesis01-executive-summary.md6

Execution Model Options

ModelWhen to UseAgent Spawn
Workflow (PRIMARY, ADR-102)Harness with the Workflow toolWorkflow({ name: "qcsd-development-review", args: { sourcePath, testPath } })
Task Tool (fallback)Claude Code sessions without Workflow supportTask({ subagent_type, run_in_background: true })
MCP ToolsMCP server availablefleet_init({}) / task_submit({})
CLITerminal/scriptsswarm init / agent spawn
Workflow execution (ADR-102)

.claude/workflows/qcsd-development-review.js runs the review as a deterministic pipeline: one finder per quality dimension (TDD adherence, complexity, coverage gaps — args.dimensions selects a subset) → 3 blind adversarial refuters per finding (Loki-mode, ADR-074: refuters see only the bare claim + evidence, never the finder's confidence or each other; uncertainty defaults to refuted) → deterministic synthesis into finding-verdict@1 envelopes (ADR-103, schemas/finding-verdict.schema.json). A finding survives only if fewer than ⌈N/2⌉ refuters kill it. The final report contains ONLY confirmed findings; killed findings are retained under killed with their refutations for audit.

Args: sourcePath (required), testPath, dimensions (subset of tdd-adherence|complexity|coverage-gaps), maxFindings per dimension (default 5).

When the Workflow tool is unavailable, fall back to the Task-tool protocol below — the report format and gates are identical, minus the adversarial verification stage (note this in the report header as verification: none).


Key Principle

Code quality is measured by evidence, not intentions. This swarm provides in-sprint quality assessment to ensure code meets engineering standards before entering the CI/CD pipeline.

© 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-development-swarm of proffesor-for-testing/agentic-qe.

  • SKILL.md
  • evals/qcsd-development-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-defect-predictor.md
  • steps/09-final-output.md

Open the folder on GitHubat commit 829d030

Compare with similar skills

Qcsd Development 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 Development Swarm compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qcsd Development Swarm this skillproffesor-for-testing/agentic-qe494—~2.5kAutomated safety check: PassMIT
Test Guidelinesgetsentry/sentry-dart873—~3.1kAutomated safety check: PassMIT
Supercovsupercorp-ai/supercov1501 repos~415Automated safety check: PassMIT
Improvementtddworks/ClaudeBar1.5k—~2.1kAutomated safety check: PassApache-2.0
Characterisation Testscitypaul/.dotfiles739—~3.6kAutomated safety check: PassCustom licence
Dev ReviewFHIR/fhir-codegen154—~5kAutomated safety check: PassMIT

Similar skills

  • Test Guidelines

    getsentry/sentry-dart

    Official

    Enforce Sentry Dart/Flutter SDK test conventions for naming, structure, and fixtures.

    873 GitHub stars~3.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Supercov

    supercorp-ai/supercov

    Measures test coverage and code quality in a repository with the supercov CLI, and turns what it finds into small, focused tests or fixes.

    150 GitHub starsUsed in 1 repo~415 tokens
    Testing & QAAuto-check passed
  • Improvement

    tddworks/ClaudeBar

    Guide for making improvements to existing ClaudeBar functionality using TDD.

    1.5k GitHub stars~2.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Characterisation Tests

    citypaul/.dotfiles

    A skill your agent uses when modifying existing code that lacks tests and you need to document its actual current behavior before making changes -- the legacy code dilemma where you need tests to…

    739 GitHub stars~3.6k tokensUpdated 6 days ago
    Testing & QAAuto-check passed
  • Dev Review

    FHIR/fhir-codegen

    Performs a two-track code-quality and QA review in the roles of a staff-level Engineering Lead and QA Lead, then synthesizes both critiques into a single analysis.md.

    154 GitHub stars~5k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Official

    Interprets .NET coverage reports to explain line and branch gaps, target arithmetic and, on request, CRAP-based risk hotspots, without rerunning tests.

    5.6k GitHub starsUsed in 1 repo~2.8k tokens
    Testing & QAAuto-check passed

More from proffesor-for-testing/agentic-qe

All 95 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.

    494 GitHub stars~1.8k tokensUpdated 4 days ago
    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.

    494 GitHub stars~1.7k tokensUpdated 4 days ago
    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.

    494 GitHub stars~2.4k tokensUpdated 4 days ago
    Auto-check passed
  • Code Review Quality

    proffesor-for-testing/agentic-qe

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

    494 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.

    494 GitHub stars~2.7k tokensUpdated 4 days ago
    Auto-check: notes
  • Database Testing

    proffesor-for-testing/agentic-qe

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

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

Questions about Qcsd Development Swarm

What does Qcsd Development Swarm do?

A skill your agent uses when monitoring in-sprint code quality with TDD adherence checks, complexity analysis, coverage gap detection, or defect prediction in the QCSD Development phase. Qcsd Development Swarm is an agent skill from proffesor-for-testing/agentic-qe. Use when monitoring in-sprint code quality with TDD adherence checks, complexity analysis, coverage gap detection, or defect prediction in the QCSD Development phase.

When should I use Qcsd Development Swarm?

Qcsd Development Swarm fits situations like: monitoring in-sprint code quality with TDD adherence checks; complexity analysis; coverage gap detection; defect prediction in the QCSD Development phase.

How do I install Qcsd Development Swarm in Claude Code?

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

How do I install Qcsd Development Swarm in Codex?

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

Can I use Qcsd Development 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-development-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-development-swarm, .gemini/skills/qcsd-development-swarm, .github/skills/qcsd-development-swarm and .opencode/skills/qcsd-development-swarm in your project.

What does Qcsd Development Swarm need to run?

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

Does Qcsd Development 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 Development 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 Development Swarm use?

Qcsd Development 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 Development Swarm use?

About 2.5k tokens (SKILL.md is roughly 10k 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 Development Swarm?

Skills that share tags, products or a category with Qcsd Development Swarm: Test Guidelines (getsentry/sentry-dart, 873 stars), Supercov (supercorp-ai/supercov, 150 stars), Improvement (tddworks/ClaudeBar, 1.5k stars) and Characterisation Tests (citypaul/.dotfiles, 739 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qcsd Development Swarm?

proffesor-for-testing (a GitHub user) maintains it in proffesor-for-testing/agentic-qe, which has 494 GitHub stars. The repository holds 95 skills in this directory. The repository was last updated on October 4, 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.