non-functional-test-planning

Plan non-functional performance and security testing against SLO targets.

1|Updated Nov 29, 2025

Search Tags:#devops #performance #security #threat-modeling #slo #test-planning #non-functional-testing

Ready to run

npx skills add https://github.com/SSiertsema/claude-code-plugins --skill non-functional-test-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: non-functional-test-planning
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/non-functional-test-planning/skills/non-functional-test-planning
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill non-functional-test-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-functional testing planning that helps teams align performance and security verification with product goals, SLO targets, and threat modeling across the lifecycle.

Core Features & Use Cases

Define product context, critical flows, and SLO targets for performance and security tests.
Outline test types (load, stress, soak, spike, scalability) and map them to threat-model coverage.
Produce a complete test strategy with tooling, environment, and governance hand-offs for risk reduction and faster delivery.

Quick Start

Provide the product name, critical flows, SLO targets, and threat model to generate a full non-functional test plan.

Frequently Asked Questions about non-functional-test-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I plan non-functional testing for performance and security against SLO targets?▼

Non-functional testing for performance and security is planned by defining product context, critical flows, and SLO targets. This process maps load and stress test types to threat-model coverage, producing a structured test strategy with governance hand-offs.

What inputs do I need to generate a complete non-functional test strategy?▼

To generate a non-functional test strategy, you must provide the product name, critical flows, SLO targets, and a threat model. These inputs drive the creation of workload modeling, thresholds, and tooling specifications.

How does SLO-driven threat modeling integrate with performance test planning?▼

SLO-driven threat modeling integrates with performance test planning by mapping security verification to workload modeling and test types like load, stress, and soak. This alignment ensures performance thresholds directly support risk reduction goals.

What is the best way to structure non-functional testing across different lifecycle phases?▼

The best way to structure non-functional testing across lifecycle phases is using a phased A/B/C governance approach. This structure organizes environment setup, tooling, and test execution to validate performance and security SLOs systematically.

Can I use this approach to map performance test types like spike and scalability to security threats?▼

Yes, this approach maps performance test types including spike, stress, soak, and scalability directly to threat-model coverage. Aligning these tests with SLO targets ensures both performance thresholds and security risks are validated.

When do I need a structured non-functional test plan for my DevOps workflow?▼

You need a structured non-functional test plan for your DevOps workflow when aligning performance and security verification with product goals is required. It establishes environment specifications, tooling, and governance hand-offs for faster delivery.