AgenticTesting

Test coverage analysis, gap detection, coverage reporting, and coverage optimization using the COVERED agent pipeline. Use this skill whenever the user mentions test coverage, coverage analysis, coverage gaps, traceability matrix, coverage heat map, coverage dashboard, coverage metrics, coverage trends, test intensity, risk-based coverage, requirement coverage, code coverage mapping, or wants to know if their testing is sufficient. Also trigger when users ask about uncovered requirements, orphaned tests, coverage regression, or coverage targets. MANDATORY TRIGGERS: coverage, traceability, gap analysis, RTM, heat map, coverage dashboard, coverage trend, test intensity evaluation.

Generate concrete test cases, test data, and test scripts from a test design technique and context. Applies 106 test design techniques (boundary value analysis, equivalence partitioning, decision tables, state transitions, pairwise, combinatorial, etc.) to enumerate test conditions and author realistic test cases with inputs, expected results, and traceability. Use this skill whenever the user needs to: create test cases from a technique, apply a testing method to requirements, generate test data, design test scenarios, or populate test scripts. Triggers include: 'test cases', 'create tests', 'test design', 'apply [technique name]', 'generate test data', 'test scenarios', or any technique name (BVA, EP, combinatorial, etc.).technique name (BVA, EP, combinatorial, etc.).

Generate comprehensive test strategies, quality engineering approaches, risk analysis, and optimal technique selection. Use this when you need to develop test strategies, perform quality risk analysis, select test design techniques, assess testability, estimate test effort, define governance structures, or establish test exit criteria and coverage targets.

Test management, defect management, process evaluation, and maturity assessment using the MANAGES agent pipeline. Use this skill whenever the user mentions test management, defect management, process improvement, TMMi, maturity assessment, ARCI matrix, quality policy, test policy, process evaluation, defect lifecycle, triage, test process, roles and responsibilities, QAM, QPM, GTA, generic test agreements, process maturity, test improvement, or wants to evaluate and improve their testing practices. Also trigger for defect tracking, anomaly management, process compliance, test governance, or organizational testing capability. MANDATORY TRIGGERS: test management, defect management, TMMi, maturity, ARCI, process improvement, quality policy, defect lifecycle, process evaluation, test governance.

Generate comprehensive test plans, schedules, resource allocation, environment setup, and test data strategies. Use this when you need to develop master test plans, level-specific test plans, allocate resources and environments, plan non-functional testing, define end-to-end testing chains, or establish test data management strategies.

Test reporting, progress dashboards, release advice, and final test reports using the REPORTS agent pipeline. Use this skill whenever the user mentions test report, progress report, test dashboard, release advice, go/no-go decision, test metrics, defect trends, test execution summary, quality assessment, final test report, lessons learned, RAG status, or wants to generate any kind of testing status or quality report. Also trigger for executive summaries, sprint test reports, release readiness, or stakeholder communication about testing. MANDATORY TRIGGERS: test report, progress, dashboard, release advice, go/no-go, test metrics, defect trend, RAG status, quality report, test summary

Generate 108 context-specific test templates: decision tables, state transition matrices, test case logs, test plans, exploratory charters, ARCI matrices, traceability sheets, and quality hunting documents. Use this skill whenever the user needs: test design worksheets, test execution logs, test strategy tables, quality engineering templates, defect tracking forms, estimation worksheets, checklists, or any test artifact. Triggers include: 'template', 'worksheet', 'form', 'test document', 'test plan', 'test case log', 'decision table', 'charter', 'matrix', 'checklist', 'strategy table', 'ARCI', or requests to 'generate a [template type]'.

OpenRequirements.AI DeFOSPAM requirements engineering validation skill using 7 specialized AI analyst agents based on the Business Story Method by Paul Gerrard. Analyzes requirements through Definitions, Features, Outcomes, Scenarios, Prediction, Ambiguity, and Missing data checks. Produces business stories, scenarios, glossaries, and gap analysis reports. Use this skill whenever the user wants to validate requirements, check requirements quality, create business stories from requirements, find ambiguity in specifications, generate test scenarios from requirements, or perform specification by example. Also trigger when the user mentions DeFOSPAM, business stories, requirements validation, specification by example, SBE, living documentation, or executable specifications — even if they don't name the skill directly.

OpenRequirements.AI DeFOSPAM requirements engineering validation skill using 7 specialized AI analyst agents based on the Business Story Method by Paul Gerrard. Analyzes requirements through Definitions, Features, Outcomes, Scenarios, Prediction, Ambiguity, and Missing data checks. Produces business stories, scenarios, glossaries, and gap analysis reports. Use this skill whenever the user wants to validate requirements, check requirements quality, create business stories from requirements, find ambiguity in specifications, generate test scenarios from requirements, or perform specification by example. Also trigger when the user mentions DeFOSPAM, business stories, requirements validation, specification by example, SBE, living documentation, or executable specifications — even if they don't name the skill directly.

OpenRequirements.AI Vibe Requirements skill using 8 specialized AI analyst agents based on Tom Gilb's Planguage Vibe Requirements methodology from the book Vibe Requirements. Transforms vague, ambiguous requirements into quantified vibe specifications with Scales, Meters, Benchmarks, Constraints, Targets, Background specs, Stakeholder analysis, and Quality Control. Takes raw requirements, user stories, or DeFOSPAM output as input and produces formal Planguage vibe specifications with numeric scales, measurable meters, benchmark levels, tolerable constraints, wish/goal/stretch targets, and stakeholder value maps. Use this skill whenever the user wants to quantify requirements, create vibe specifications, define measurable scales for qualities, convert user stories into Planguage, assess requirement quality using Spec QC, prioritize requirements by value, or produce Gilb-style quantified specifications.

OpenRequirements.AI Performance Engineering skill using 8 specialized AI analyst agents based on the Effective Performance Engineering methodology by Todd DeCapua and Shane Evans. Analyzes non-functional requirements (NFRs) across 8 performance engineering disciplines: Capacity, Latency, Availability, Scalability, Security, Usability, Monitoring, and Endurance. Takes DeFOSPAM output (openrequirements-results.json) or raw NFRs as input and produces performance budgets, SLA definitions, capacity models, and a comprehensive NFR assessment. Use this skill whenever the user wants to analyze non-functional requirements, create performance budgets, define SLAs, assess capacity planning needs, evaluate scalability, check security performance implications, design monitoring strategies, plan load testing, or produce performance engineering documentation.

OpenRequirements.AI Requirements Specification skill using 8 specialized AI analyst agents based on IEEE Std 830-1998 Recommended Practice for Software Requirements Specifications. Transforms DeFOSPAM requirements validation output (openrequirements-results.json) into a formal IEEE 830-compliant Software Requirements Specification (SRS) document. Agents assess the 8 characteristics of a good SRS: Correct, Unambiguous, Complete, Consistent, Ranked, Verifiable, Modifiable, and Traceable. Produces a structured SRS document with quality assessment, traceability matrix, and gap analysis. Use this skill whenever the user wants to create a formal requirements specification, generate an SRS document, assess requirements quality against IEEE 830, check requirements for completeness or consistency, build a traceability matrix, rank requirements by importance, or produce IEEE-compliant documentation.

OpenRequirements.AI Specification by Example (SBE) skill using 7 specialized AI analyst agents based on the key process patterns from Specification by Example methodology. Transforms DeFOSPAM requirements validation output (openrequirements-results.json) into executable specifications, living documentation, and refined examples. Agents cover: Deriving scope goals, Specifying collaboratively, Illustrating examples, Refining the specification, Automating validation without changing specifications, Validating frequently and Evolving a documentation system. Use this skill whenever the user wants to create executable specifications from requirements, generate living documentation and produce Gherkin feature files, create specification workshops, build acceptance criteria from DeFOSPAM output, or transform business stories into specifications. Generation of specification by example, SBE, executable specifications, living documentation, Gherkin, feature files, ATDD or BDD.

OpenRequirements.AI DeFOSPAM requirements engineering validation skill using 7 specialized AI analyst agents based on the Business Story Method by Paul Gerrard. Analyzes requirements through Definitions, Features, Outcomes, Scenarios, Prediction, Ambiguity, and Missing data checks. Produces business stories, scenarios, glossaries, and gap analysis reports. Use this skill whenever the user wants to validate requirements, check requirements quality, create business stories from requirements, find ambiguity in specifications, generate test scenarios from requirements, or perform specification by example. Also trigger when the user mentions DeFOSPAM, business stories, requirements validation, specification by example, SBE, living documentation, or executable specifications — even if they don't name the skill directly.