Claude Code Plugins

Community-maintained marketplace

Feedback

qa-validation

@Ddell12/MedHarmony
0
0

Comprehensive quality assurance and validation workflow between implementation and deployment. Validates code against specifications, performs security audits, measures quality metrics, and generates deployment readiness reports. Use after implementation is complete and before deployment begins.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name qa-validation
description Comprehensive quality assurance and validation workflow between implementation and deployment. Validates code against specifications, performs security audits, measures quality metrics, and generates deployment readiness reports. Use after implementation is complete and before deployment begins.
license MIT
metadata [object Object]

Quality Assurance & Validation Skill v2.0

Orchestrated Workflow Edition - Production Readiness Gateway

Purpose

This skill provides comprehensive quality assurance and validation between implementation completion and deployment, ensuring code meets specifications, passes security audits, and is production-ready.

Key Features:

  • ✅ 6-Phase Validation Workflow - From prerequisite checks to deployment readiness
  • ✅ Automated Quality Checks - Test coverage, type safety, linting, bundle analysis
  • ✅ Spec Compliance Verification - Validates implementation matches PRD and architecture
  • ✅ Security & Performance Audits - OWASP checks, performance benchmarks
  • ✅ Regression Testing - E2E tests, integration tests, user flows
  • ✅ Deployment Readiness Scoring - Go/no-go decision with clear criteria
  • ✅ State Management - Resume validation at any phase
  • ✅ Comprehensive Reports - Quality metrics, compliance, security, readiness

Foundation: Bridges implementation skill (code generation) and deployment skill (production release) with enterprise-grade quality gates.

When to Use This Skill

Activate this skill when:

  • ✅ Implementation skill Phase 3 complete (all stories implemented)
  • ✅ All tests passing in implementation
  • ✅ Build successful
  • ✅ Ready to validate for production deployment

Trigger Phrases:

  • "Validate my implementation for deployment"
  • "Run QA validation on [project name]"
  • "Check deployment readiness for [project]"
  • "Perform quality assurance before deployment"

Prerequisites:

  • Implementation skill completed
  • impl_state.json shows status = "completed"
  • All planning artifacts exist (PRD, Architecture, Data Models)
  • Code committed to git

MCP Server Requirements

Required MCP Servers

  • None - This skill works without MCP servers

Optional MCP Servers

MCP Server Purpose Benefit Fallback
GitHub Create QA tracking issues, post validation reports Team visibility into QA process Manual gh commands

MCP Server Detection

See: MCP Integration

At skill initialization, the workflow checks for MCP availability and uses fallbacks when needed.

State Dependencies (CRITICAL)

See: State Dependencies

This skill depends on specific fields from implementation and spec-planning state files. These dependencies are explicitly documented to prevent breakage if state structures change.

Required from impl_state.json:

  • status = "completed"
  • completed_stories
  • test_results
  • validation.* (tests_passed, build_successful, type_check_passed, lint_passed, security_check)

Required from spec_state.json:

  • current_phase = "completed"
  • patterns_applied
  • decisions_made
  • documents_generated (prd, architecture, data_models, ui_specifications, development_stories)

Full validation rules and breaking change policy in reference file.

Validation Workflow Overview

6-Phase Validation Process

Phase Name Duration Checks Reference
1 Prerequisite Validation 10-15 min State files, impl status Phase 1
2 Automated Quality Checks 20-30 min Tests, lint, types, bundle Phase 2
3 Spec Compliance 30-45 min PRD match, arch compliance Phase 3
4 Security & Performance 45-60 min OWASP, performance benchmarks Phase 4
5 Regression Testing 30-60 min E2E tests, integration tests Phase 5
6 Deployment Readiness 15-30 min Go/no-go decision Phase 6

Total Time: 2.5-3.5 hours Value: Prevents production issues, ensures quality, validates completeness

Quick Start

Starting Validation

User: "Validate my implementation for deployment"

Claude will:
1. Check for impl_state.json (implementation completed)
2. Load planning artifacts (PRD, Architecture, Data Models)
3. Initialize qa_state.json
4. Begin Phase 1 (Prerequisite Validation)

Resuming Validation

User: "Continue QA validation for [project-name]"

Claude will:
1. Load qa_state.json
2. Display current phase and progress
3. Resume from current phase

Phase Workflows

Phase 1: Prerequisite Validation

Objective: Verify all prerequisites before starting QA validation Duration: 10-15 minutes See: Phase 1 Workflow

Validates implementation and planning states, checks all required documents exist. This is a binary gate - either 100% pass or validation exits with clear errors.

Key Checks:

  • Implementation complete (status = "completed")
  • All tests passing
  • Build successful
  • Type check passing
  • Planning complete
  • All documents exist

Validation Gate: Must be 100% to proceed

Phase 2: Automated Quality Checks

Objective: Run automated quality analysis and generate metrics Duration: 20-30 minutes See: Phase 2 Workflow

Runs comprehensive automated checks on code quality, test coverage, bundle size, and dependencies.

Key Checks:

  • Test suite with coverage analysis (target: ≥80%)
  • TypeScript type checking (zero errors)
  • ESLint with strict rules
  • Bundle size analysis (target: <500kb)
  • Dependency vulnerability scan
  • Database query optimization check

Output: reports/quality-metrics-report.md Validation Gate: ≥75% to proceed

Phase 3: Spec Compliance Verification

Objective: Verify implementation matches specifications exactly Duration: 30-45 minutes See: Phase 3 Workflow

Compares implementation against planning documents to ensure all requirements are met and patterns followed.

Key Verification:

  • PRD requirements checklist (all features implemented?)
  • Architecture pattern compliance (API, database, security)
  • Data model accuracy (exact table/field names)
  • UI specification matching (components, pages, layouts)
  • API endpoint validation (match architecture)

Output: reports/spec-compliance-report.md Validation Gate: ≥80% to proceed (highest weight in overall score)

Phase 4: Security & Performance Audit

Objective: Comprehensive security and performance validation Duration: 45-60 minutes See: Phase 4 Workflow

Performs security audits and performance benchmarking to ensure production readiness.

Key Audits:

  • OWASP Top 10 security checks
  • Authentication/authorization review
  • RLS policy validation
  • Performance benchmarking (page load, API response)
  • Accessibility testing (WCAG 2.1 AA)
  • SEO validation

Output: reports/security-audit-report.md, reports/performance-report.md Validation Gate: No critical vulnerabilities

Phase 5: Regression & Integration Testing

Objective: Validate all features work together without regressions Duration: 30-60 minutes See: Phase 5 Workflow

Executes E2E tests and integration tests to verify system-wide functionality.

Key Tests:

  • E2E test suite execution
  • Cross-browser compatibility
  • Mobile responsiveness
  • User flow validation
  • API integration tests
  • Database migration verification

Output: reports/test-results-report.md Validation Gate: ≥90% tests passing

Phase 6: Deployment Readiness Assessment

Objective: Final readiness evaluation and go/no-go decision Duration: 15-30 minutes See: Phase 6 Workflow

Calculates overall readiness score and makes deployment recommendation.

Assessment:

  • Calculate overall readiness score (0-100%)
  • Identify blockers vs warnings
  • Generate pre-deployment checklist
  • Optional stakeholder sign-off workflow
  • Make go/no-go decision

Output: reports/deployment-readiness-report.md + Go/No-Go decision

Decisions:

  • GO (≥90%): Proceed to deployment
  • CONDITIONAL GO (75-89%): Review warnings, then deploy with caution
  • NO-GO (<75%): Fix blockers before deployment

Retry Workflow After NO-GO

See: Retry Workflow

When Phase 6 returns a NO-GO decision:

  1. Blockers are documented in qa_state.json with remediation guidance
  2. User fixes identified issues
  3. User triggers targeted re-validation (specific phases only) or full re-validation
  4. New readiness score determines go/no-go decision

Targeted Re-Validation (Recommended): Re-run only failed phases for faster validation Full Re-Validation: Re-run all 6 phases for complete audit

Full workflow details, recovery options, and retry best practices in reference file.

Quality Metrics & Scoring

See: Quality Metrics

Overall readiness score uses weighted formula: Phase 3 (Spec Compliance) is most critical at 30%, followed by Phases 2 and 4 at 25% each. Full scoring formulas, quality targets, and decision thresholds in reference file.

State Management

See: State Management

State Location: .claude/qa-validation/state/{project-name}/qa_state.json

Key Operations:

  • Initialize: Create new state from template
  • Load: Resume from existing state
  • Update: Track progress after each phase
  • Retry: Reset specific phases for re-validation

State Schema: See State Template

The state tracks all validation attempts, phase scores, blockers, warnings, and deployment readiness decision.

MCP Integration

See: MCP Integration

Supports GitHub MCP for enhanced team visibility:

  • Create QA tracking issues
  • Post validation reports as comments
  • Update readiness status
  • Close issue on completion

Falls back to gh CLI or github-issue-manager skill if MCP not available.

Report Templates

Seven report templates generate validation outputs for each phase (see templates/ directory). Templates use progressive disclosure - loaded only when needed, not at workflow start.

Error Handling

See: Error Handling

The skill handles five error categories: validation failures, missing prerequisites, missing artifacts, tool/command failures, and state corruption. All errors provide clear guidance for remediation with specific recovery options. Full error handling procedures and recovery workflows in reference file.

Reference Files

Core Concepts (5 files)

Location: references/core/

Foundation concepts and system design:

Phase Workflows (6 files)

Location: references/phases/

Detailed step-by-step workflow instructions:

Sub-Workflows (1 file)

Location: references/workflows/

Specialized workflow procedures:

Templates (7 files)

Location: templates/

Reusable templates and configurations:

Success Metrics

Validation is successful when:

  • ✅ All 6 phases completed
  • ✅ Overall readiness score ≥90%
  • ✅ No blocking issues
  • ✅ Test coverage ≥80%
  • ✅ Spec compliance ≥95%
  • ✅ No critical security vulnerabilities
  • ✅ Performance metrics within targets
  • ✅ All E2E tests passing
  • ✅ Stakeholder sign-off obtained (if required)
  • ✅ Go decision made

Integration with Skills

From implementation Skill

Inputs: impl_state.json, implemented code, build artifacts, git commits

Trigger: implementation Phase 3 complete

To deployment Skill

Outputs: qa_state.json, validation reports, pre-deployment checklist, Go/No-Go decision

Trigger: Phase 6 complete + readiness score ≥90%

With spec-planning Skill

Uses planning artifacts: prd.md, architecture.md, data-models.md, ui-specifications.md, development-stories.md

With github-issue-manager Skill

GitHub Integration (optional): Create QA tracking issue, post reports, update status

Version History

v2.0.1 (2025-10-29):

  • Further optimized to <450 lines (was 542 lines)
  • Moved retry workflow to dedicated reference file
  • Created comprehensive error handling reference
  • Condensed inline sections for better progressive disclosure
  • Organized 5 core concepts + 6 phases + 1 workflow reference
  • Improved file organization and consistency

v2.0.0 (2025-10-29):

  • Refactored to progressive disclosure pattern
  • Organized reference and template files
  • Added Phase 1: Prerequisite Validation
  • Enhanced state dependency documentation
  • Improved quality metrics and scoring system

v1.0.0 (2025-10-29):

  • Initial release with orchestrated workflow
  • 5-phase validation process
  • Automated quality checks
  • Spec compliance verification
  • Security and performance audits
  • Regression testing
  • Deployment readiness assessment
  • State management
  • Integration with existing skills
  • Comprehensive reporting

Version: 2.0.0 Last Updated: 2025-10-29 Maintained by: Personal Workflow Workflow Mode: Orchestrated (Quality Gates) Requires: spec-planning, implementation skills Integrates With: deployment, github-issue-manager skills