qa-ai-stlc
v0.4.0Open-source, model-agnostic QA framework: explorer, test design, execution and reporting.
By The QA-AI-STLC AuthorsLicense: Apache-2.00 GitHub starsUpdated yesterday
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 4 skill or MCP entries
- Source updated
- Sep 22, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install qa-ai-stlc for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install qa-ai-stlc@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/Klim-101/QA-AI-STLCClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is adapters/claude-plugin/.
Plugin files
├── .claude-plugin/plugin.json├── skills/qa-design-cases/SKILL.md├── skills/qa-explore/SKILL.md├── skills/qa-start/SKILL.md└── .mcp.json
Included Skills3
Use when the operator wants test cases written or updated ("design test cases for the checkout flow", "write cases for this requirement", "add a regression case for X"). Never use to start a session (`qa-start`), build the registry (`qa-explore`), or execute an already-written case.
Use when the operator wants to build or refresh the selector registry ("explore the app", "crawl the app for testable elements", "update the registry", "check if the registry is still valid", "why doesn't this locator work anymore"). Never use for starting a new session (that is `qa-start`) or for case design / execution work once elements already exist in the registry.
Use when the operator wants to start, resume, or check the status of a QA-AI-STLC session ("start testing this app", "let's begin QA", "where did we leave off", "what's the current phase"). Also use when no `.qa/` project exists yet and the operator wants one set up. Never use once a session is already running and the operator names a concrete exploration or case-design task — dispatch that directly to `qa-explore` or `qa-design-cases` instead of re-entering this skill.
MCP servers1
- command
- npx
- args
- -y @qa-ai-stlc/[email protected]
- env.QA_EXPECTED_ENGINE_VERSION
- 0.4.0
Plugin manifests1
{
"name": "qa-ai-stlc",
"displayName": "QA-AI-STLC",
"version": "0.4.0",
"description": "Open-source, model-agnostic QA framework: explorer, test design, execution and reporting.",
"author": {
"name": "The QA-AI-STLC Authors"
},
"homepage": "https://github.com/Klim-101/QA-AI-STLC",
"repository": "https://github.com/Klim-101/QA-AI-STLC",
"license": "Apache-2.0",
"keywords": [
"qa",
"testing",
"playwright",
"mcp",
"e2e"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[qa-ai-stlc on Agent Plugins Marketplace](https://pluginsmp.com/plugins/qa-ai-stlc)