Design and validate container-scoped test plans with standardized templates.
npx skills add https://github.com/wtah/spec-master --skill test-planning-skill
Please help me install this Agent Skill. Skill: Test Planning Skill Source: https://github.com/wtah/spec-master/tree/main/.claude/skills/test-planning Command: npx skills add https://github.com/wtah/spec-master --skill test-planning-skill
This skill helps teams design and validate container-scoped test plans, reducing risk and accelerating delivery.
Generate a new test plan for a container by applying the provided templates and naming conventions, then populate sections for responsibilities, flows, and error handling.
High-intent search queries and answers about installing and using this skill.
To create a container test plan, apply the provided templates and naming conventions, then populate sections for responsibilities, flows, and error handling. This enforces a standardized structure with clear IDs for component and container level validation.
Container-scoped test planning is the process of designing and validating tests within container boundaries. You need it when validating component reliability and integration patterns to reduce risk and accelerate delivery without exceeding container scope.
Prioritize integration tests by applying P0, P1, P2, and P3 focus levels to maximize container reliability. This guidance helps teams allocate testing resources effectively across component and container level test plans.
Yes, you can use mock patterns and fixtures for black box testing inside a container. The skill provides conventions for fixtures, mocks, and integration patterns that stay within container boundaries during test execution.
Yes, this test planning approach works without external dependencies. It operates independently to help teams design test plans, providing templates and reporting conventions that stay within container boundaries.
The limitation of enforcing test plans within container boundaries is that integration patterns and test execution must stay inside the container scope. This approach focuses on component and container level validation rather than broader system-wide testing.
wtahStandardize container boundary tests for HTTP endpoints, webhooks, and queue consumers.
cosmixCreate unit, integration, and end-to-end test suites across languages and frameworks.
KeyValueSoftwareSystemsDerive black-box functional test cases from acceptance criteria and design artifacts.
MazenMradDesign system-level or epic-level test plans from PRD/ADR context.
