Skip to main content

test-readability-and-clarity-check-approach

The Test Readability and Clarity Check is a dual-agent validation approach that assesses whether a test suite effectively documents system behavior by reconstructing system understanding purely fro...

Datos de origen

Repositorio
sddevelopment-be/quickstart_agent-augmented-development
Última actividad en el origen
31 de enero de 2026 a las 06:30
Idioma detectado de SKILL.md
inglés
Estrellas
13
Forks
3

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
Test Readability and Clarity Check Approach
description
The Test Readability and Clarity Check is a dual-agent validation approach that assesses whether a test suite effectively documents system behavior by reconstructing system understanding purely fro...
version
1.0.0
type
approach
category
quality-validation-pattern
# Test Readability and Clarity Check Approach The Test Readability and Clarity Check is a dual-agent validation approach that assesses whether a test suite effectively documents system behavior by reconstructing system understanding purely fro... ## Instructions The Test Readability and Clarity Check is a dual-agent validation approach that assesses whether a test suite effectively documents system behavior by reconstructing system understanding purely from test code. This approach validates that tests serve as executable specifications and identifies gaps in architectural context documentation. **Key Insight: ** Tests that allow accurate system reconstruction without external documentation prove their quality as living specification documents. --- ## Principles 1. Test-as-Documentation 2. Separation of Concerns 3. Dual Perspective 4. Measurable Outcomes 5. Actionable Feedback ## When to Use - Major test suite refactoring completed (validate improvement) - New team members onboarding (generate system overview) - Architecture documentation audit needed (find alignment gaps) - Quality gate before major release (comprehensive validation) - Quarterly quality reviews (track test suite evolution)
Ver en GitHub