staging-validation-phase

Standard Operating Procedure for staging validation. Manual testing before production.

⭐0stars🔀0forks📁View on GitHub🕐Updated Nov 24, 2025

When & Why to Use This Skill

This Claude skill provides a structured Standard Operating Procedure (SOP) for staging environment validation, designed to ensure software quality before production deployment. It guides users through critical manual testing phases, including smoke tests, data migration verification, and rollback capability checks, to minimize the risk of post-release incidents.

Use Cases

  • Pre-production smoke testing: Systematically verifying that the core functionalities of a new build are stable on the staging server.
  • Critical flow validation: Testing essential user journeys and business logic to ensure no regressions were introduced during the latest update.
  • Data migration auditing: Verifying that database schema changes and data migrations have executed correctly before applying them to production.
  • Release sign-off: Providing a documented validation report and formal approval process for release managers and stakeholders.
namestaging-validation-phase
description"Standard Operating Procedure for staging validation. Manual testing before production."
allowed-toolsRead, Edit, Bash

Staging Validation Phase: Standard Operating Procedure

Training Guide: Validate staging deployment before promoting to production.

Phase Overview

Purpose: Manual testing on staging, smoke tests, sign-off Inputs: Staging deployment Outputs: Validation report, sign-off decision Expected duration: 30-60 minutes

Execution Steps

  1. Run smoke tests on staging
  2. Test critical user flows
  3. Verify data migrations
  4. Check rollback capability
  5. Sign-off decision (approve/reject)

Common Mistakes

  • Validation steps skipped
  • Smoke tests insufficient
  • Sign-off unclear

Completion Criteria

  • Smoke tests pass
  • Critical flows verified
  • Sign-off documented

This SOP guides staging validation.