capability-assess-testing

Assess and adopt a testing framework, coverage strategy, and pyramid distribution for a project.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/learnn-com/engineering-kb --skill capability-assess-testing-learnn-com
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capability-assess-testing
Source: https://github.com/learnn-com/engineering-kb/tree/main/.skills/capability-assess-testing
Command: npx skills add https://github.com/learnn-com/engineering-kb --skill capability-assess-testing-learnn-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing and documenting a testing strategy is often inconsistent across projects. This Skill standardizes the decision by evaluating testing frameworks against the adopted tech stack, writing the testing section of tech-stack.md, and recording the decision as an ADL or ADR. ## Core Features & Use Cases - Resolution Cascade: Resolves the testing decision via explicit argument override, existing adoption detection, or full assessment from guidelines, making the workflow idempotent. - Framework Evaluation: Compares compatible frameworks (e.g. Vitest, Jest, Playwright, Cypress) on speed, DX, coverage tooling, and TypeScript support, then proposes pyramid distribution and coverage targets. - Adoption & Decision Recording: Writes only the Testing section of tech-stack.md while preserving other sections, and composes /capability-record-decision to log the decision. - Use Case: During project bootstrap, run the assessment to select Vitest with an 80% coverage target, update tech-stack.md, and automatically backfill the decision record. ## Quick Start Run the testing assessment to evaluate frameworks for my TypeScript project and record the adopted testing strategy in tech-stack.md.

Frequently Asked Questions about capability-assess-testing

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

FAQPage Schema
How do I choose a testing framework for a TypeScript project?▼

Evaluate compatible frameworks such as Vitest, Jest, Mocha, Playwright, and Cypress against speed, developer experience, coverage tooling, and TypeScript support. The assessment reads testing guidelines and your adopted tech stack, then presents a recommendation with rationale for approval.

How do I set a test pyramid and coverage target for my project?▼

Define the distribution as unit tests greater than integration tests greater than E2E tests, with an explicit minimum coverage percentage. The strategy proposal includes pyramid ratios and a coverage target derived from the test-strategy guidelines.

Can I override the assessment with a specific framework like Vitest?▼

Yes, pass the framework name as the choice argument to skip the full assessment and adopt it directly. If an existing different framework is already recorded, you will be asked to confirm the override before the testing section is updated.

What happens if a testing strategy is already adopted?▼

The skill detects the populated Testing section in tech-stack.md and confirms the existing adoption instead of re-assessing. If the matching decision record is missing, it backfills one through the decision-recording skill.

Does the testing assessment modify other sections of tech-stack.md?▼

No, it writes only the Testing section and preserves all other content. Core sections are owned by the stack assessment skill and the AI section by the AI assessment skill.

What if the chosen testing framework is incompatible with my language?▼

The assessment halts and warns about the incompatibility, then suggests compatible alternatives for the adopted language and framework. No adoption file changes are written until a compatible choice is confirmed.