skills.rest
wendeus0
wendeus0COMMUNITY
Explore all skills by this author →
GitHub

test-architecture-plan

Plan and document a testing architecture with TESTING_PLAN.md and feature artifacts.

Updated Aug 23, 2026
Search Tags:#planning#documentation#risk-assessment#ci-cd#project-management#testing-architecture
One-click install
npx skills add https://github.com/wendeus0/AI-dotfiles --skill test-architecture-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-architecture-plan
Source: https://github.com/wendeus0/AI-dotfiles/tree/main/core/skills/test-architecture-plan
Command: npx skills add https://github.com/wendeus0/AI-dotfiles --skill test-architecture-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill focuses on producing a complete, structured testing architecture plan for projects that lack a formal strategy, enabling teams to align on approach and governance.

Core Features & Use Cases

  • Produces a root-level TESTING_PLAN.md that consolidates stack, risks, tools, and criteria.
  • Generates the four required artifacts under the correct feature path: SPEC.md, PLAN.md, and TASKS.md inside features/NNN-testing-strategy, plus a prioritized adoption checklist.
  • Provides a clear, repeatable process to map the project and establish gates for CI/CD and release readiness.

Quick Start

Generate a complete TESTING_PLAN for the current project and create the four required artifacts in the features directory.

Frequently Asked Questions about test-architecture-plan

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

FAQPage Schema
How do I create a testing architecture plan for a project with no formal strategy?▼

A robust testing architecture maps the project stack, assesses risks, recommends tools, and sets CI/CD gates, outputting a root TESTING_PLAN.md and SPEC.md, PLAN.md, and TASKS.md under features/NNN-testing-strategy.

What documents do I need for a comprehensive testing strategy?▼

A comprehensive testing strategy requires a root-level TESTING_PLAN.md to consolidate the stack and risks, plus SPEC.md, PLAN.md, TASKS.md, and a prioritized adoption checklist inside features/NNN-testing-strategy.

How do I assess testing risks and set CI/CD gates for project management?▼

Assess testing risks by mapping the project stack and documenting criteria, then establish CI/CD gates and release readiness checks within the testing architecture plan and prioritized adoption checklist.

Can I use this testing architecture planning process for an existing repository?▼

Yes, the process applies to existing repositories lacking a formal testing strategy, generating a root TESTING_PLAN.md and feature-level documents to establish governance and adoption criteria.

What's the best way to document tool recommendations and adoption criteria for testing?▼

Document tool recommendations and adoption criteria by consolidating them into a root TESTING_PLAN.md and a prioritized adoption checklist under features/NNN-testing-strategy for clear governance.

Related Skills

Explore More Software Engineering Skills→
lasswelltlasswellt
1

codebase-map

Analyze a codebase across technology, architecture, quality, and concerns to generate CODEBASE-MAP.md.

Community
Advanced
summarybotngsummarybotng
2

qcsd-cicd-swarm

Analyze CI/CD pipeline artifacts and issue RELEASE, REMEDIATE, or BLOCK decisions.

Official
Advanced
cfardevcfardev

cu-edit

Modify use case markdown files and synchronize roadmap status.

Community
Intermediate
voidrotvoidrot

breakdown-test

Create test strategies and QA task breakdowns using ISTQB and ISO 25010.

Community
Advanced