Testing Strategy Composer

Generate testing strategies and scaffolding from system descriptions and tech stacks.

6|Updated Oct 25, 2025

Search Tags:#testing #unit-tests #integration-tests #e2e-tests #test-strategy #test-pyramid #performance-tests

Ready to run

npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill testing-strategy-composer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Testing Strategy Composer
Source: https://github.com/williamzujkowski/cognitive-toolworks/tree/main/skills/testing-strategy-composer
Command: npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill testing-strategy-composer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing Strategy Composer helps development teams design, validate, and generate structured testing strategies and scaffolding templates that reduce test debt and accelerate release cycles.

Core Features & Use Cases

Generate a balanced test pyramid (unit, integration, e2e) tailored to your system.
Produce framework-specific scaffolding for unit/integration/e2e tests.
Output measurable gaps, execution plans, and reusable templates for CI/CD.

Quick Start

Describe your system description and tech stack to generate a complete, production-ready testing strategy.

Frequently Asked Questions about Testing Strategy Composer

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

FAQPage Schema

How do I create a balanced test pyramid for a microservices architecture?▼

Create a balanced test pyramid by analyzing your system description and tech stack to proportionally distribute unit, integration, and e2e tests. This ensures a structured testing strategy that reduces test debt and accelerates release cycles.

What is the best way to scaffold automated tests for a new software project?▼

The best way to scaffold automated tests is generating framework-specific templates for unit, integration, and e2e tests. This produces reusable code scaffolding and Markdown execution plans to guide implementation.

Does this testing strategy approach work for both monoliths and microservices?▼

Yes, this testing strategy approach works for monoliths, microservices, APIs, and UI-heavy apps. It analyzes specific system descriptions to produce tailored test pyramids and phased execution plans.

How do I measure gaps in my current test coverage and plan execution?▼

Measure coverage gaps by outputting JSON-compatible metrics that identify missing test layers. Use these metrics alongside the generated Markdown execution plan to phase your testing implementation.

Can I generate CI/CD test templates from a system description and tech stack?▼

Yes, you can generate CI/CD test templates by providing your system description and tech stack. The output includes reusable scaffolding templates and structured execution plans formatted in Markdown.

When should I not use an automated test pyramid strategy?▼

Avoid an automated test pyramid strategy when your project lacks a defined tech stack or system description. The strategy requires structured frontmatter-based metadata and clear architectural context to generate valid scaffolding.