krci-qa

Plugin krci-qa from marketplace kuberocketci-plugins in KubeRocketCI/claude-plugins. Commands read from the repo's manifest — 5 days ago.

Skills (9)

• Create Test Plan

  This skill should be used when the user asks to "create a test plan", "write a test plan", "plan testing for a story or epic", "define test scope", "set entry/exit criteria", or "define quality gates". Produces one test-plan document — scope, risk-based strategy, resource plan, and measurable qualit

• Edit Testing Settings

  This skill should be used when a testing README already exists and needs changes — "update the testing README", "change the test tags", "adjust testing conventions", "modify the tagging strategy", or "add a section to the testing README". Interactively edits README sections with a backup and per-sec

• Execute Testing

  This skill should be used when the user asks to "execute test cases", "run the test cases", "record pass/fail results", "perform a test run", or "produce a test execution report". Executes approved test cases, records results with evidence, and produces a test execution report with a quality assessm

• Generate Auto Test Cases

  This skill should be used when the user asks to "generate Gherkin scenarios", "write feature files", "extend Gherkin coverage", "add BDD scenarios for a story", "write automated test cases", or "automate test cases as Gherkin". Discovers existing coverage in the `.feature` suite (Glob/Grep), then wr

• Generate Test Cases

  This skill should be used when the user asks to "write manual test cases", "create a test cases document", "document test steps and expected results", or "turn acceptance criteria into manual test steps" — and it is the default for a bare "write test cases" / "generate test cases" when no automation

• Onboard Testing

  This skill should be used when `.feature` files already exist but there is no testing README — "onboard existing tests", "set up testing for an existing Gherkin suite", "generate a README from our existing suite", "analyze our existing BDD suite", or "import or migrate a Gherkin suite". Scans the su

• Report Defects

  This skill should be used when the user asks to "report a defect", "log a bug", "write a bug report", "classify defect severity and priority", or "assess defect impact". Produces structured defect reports — reproduction steps, severity/priority, impact analysis, and release-readiness recommendation

• Setup Testing

  This skill should be used only when no `.feature` files exist yet (a greenfield BDD setup) — "set up testing from scratch", "initialize BDD testing for a project with no feature files", "create the feature directory structure", or "first-time BDD setup". Runs a wizard to choose a features directory,

• Testing Methodologies

  This skill should be used when the user asks about test design techniques (e.g. "equivalence partitioning", "boundary value analysis", "pairwise testing"), "explain QA best practices", "what testing standards to follow", or "which testing approach to use". It is the shared knowledge base the other Q

Subagents (2)

• automation-qa-engineer

  Use this agent for executable Gherkin/`.feature` BDD automation and its workspace: generating or extending Gherkin scenarios from story acceptance criteria, setting up a new testing workspace, onboarding an existing feature suite into a testing README, and editing that README's conventions. For manu

• qa-engineer

  Use this agent for manual, document-based quality assurance: test plans, manual (Markdown) test cases, test execution reports, and defect reports. It produces QA documents that validate Story acceptance criteria and support release-readiness decisions. For executable Gherkin/`.feature` BDD automatio

Similar plugins