skills.rest
lshtram
lshtramCOMMUNITY
Explore all skills by this author →
GitHub

test-architect

Design pre-code testing strategies covering unit, integration, and end-to-end tests.

Updated Jan 21, 2026
Search Tags:#testing#e2e#qa#scaffolding#unit-testing#integration-testing#test-strategy
One-click install
npx skills add https://github.com/lshtram/core_dev --skill test-architect-lshtram
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-architect
Source: https://github.com/lshtram/core_dev/tree/main/.agent/skills/test-architect
Command: npx skills add https://github.com/lshtram/core_dev --skill test-architect-lshtram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures teams design and align a robust testing plan before implementation, preventing defects and rework by clarifying scope early.

Core Features & Use Cases

  • Layered testing strategy across unit, integration, and end-to-end tests with clear ownership.
  • Scaffolded test skeletons and coverage planning for common feature scenarios, including edge cases and security considerations.
  • A reusable blueprint that QA and development teams can adapt for diverse projects.

Quick Start

Outline a pre-code testing strategy by defining unit, integration, and end-to-end coverage goals and scaffolding templates for the next feature.

Frequently Asked Questions about test-architect

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

FAQPage Schema
How do I plan a pre-code testing strategy for a new software feature?▼

You plan a pre-code testing strategy by defining coverage goals across unit, integration, and end-to-end layers, mapping tests to specific layers, and scaffolding test skeletons to prevent defects early in the software development lifecycle.

What is included in a comprehensive test strategy document?▼

A comprehensive test strategy document includes layered ownership for unit, integration, and end-to-end tests, coverage planning for happy-path scenarios, edge cases, security considerations, and reproducible test skeletons for QA and development teams.

How do I scaffold test skeletons for happy-path and edge case scenarios?▼

You scaffold test skeletons by mapping test scenarios to their respective architectural layers and generating structured templates that cover happy-path scenarios, edge cases, and security considerations before writing the actual application code.

Does this testing strategy approach work for unit, integration, and e2e tests?▼

Yes, this testing strategy approach works across unit, integration, and end-to-end testing by enforcing clear ownership and mapping coverage requirements to each specific layer within the software development lifecycle.

Why define a testing plan before writing any implementation code?▼

Defining a testing plan before writing implementation code ensures teams align on scope and quality early, preventing defects and reducing rework by clarifying test coverage and expectations before development starts.

Related Skills

Explore More Software Engineering Skills→
Kandil7Kandil7
11

Feature Implementation Automation

Generate Flutter domain, data, and presentation layers from IMPLEMENTATION_PLAN.md specifications.

Community
Advanced
etylsarinetylsarin
59

testing-workflow

Plan, execute, and validate unit, integration, and E2E tests for feature releases.

Community
Advanced
haidonglethqbhaidonglethqb

ck:test

Automate unit, integration, e2e, and UI tests with coverage analysis.

Community
Advanced
ArabelaTsoArabelaTso
142

coverage-enhancer

Analyze test suites and source code to suggest unit tests for uncovered branches.

Community
Intermediate