aid-qa-ship

AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.

⭐5stars🔀0forks📁View on GitHub🕐Updated Jan 8, 2026⬇️1downloads

When & Why to Use This Skill

The QA & Ship Phase skill is a comprehensive framework designed to streamline the final stages of the software development lifecycle. It provides structured methodologies for validating implementations, conducting acceptance tests, and managing the release process. By integrating rigorous checklists for functional and non-functional requirements, it ensures production readiness, minimizes deployment risks, and facilitates high-quality software delivery with clear documentation and stakeholder alignment.

Use Cases

  • Acceptance Testing: Systematically verifying that new features meet all defined user stories and technical requirements before moving to production.
  • Release Management: Coordinating the end-to-end deployment workflow, including staging verification, smoke testing, and production monitoring.
  • Documentation & Compliance: Automatically generating professional release notes, changelogs, and certification checklists for stakeholder approval.
  • Operational Readiness: Assessing performance, security, and accessibility to ensure the application can handle production traffic and meets compliance standards.
  • Post-Deployment Audit: Managing the immediate post-release phase by monitoring error logs, gathering user feedback, and documenting lessons learned for continuous improvement.
nameaid-qa-ship
descriptionAID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.

QA & Ship Phase Skill

Phase Overview

Purpose: Validate implementation meets requirements, ensure production readiness, ship with confidence.

Entry: Development complete, tests passing, code reviewed Exit: Acceptance criteria verified, no blockers, deployed, stakeholders informed

Deliverables

  1. Test Results - All acceptance criteria covered
  2. Release Certification - Checklist, stakeholder approvals
  3. Release Notes - User-facing changelog
  4. Deployment - Verified, monitoring active

QA Testing Checklist

Functional

  • All user stories verified
  • All acceptance criteria tested
  • Edge cases covered
  • Error handling tested
  • Cross-browser/device (if applicable)

Non-Functional

  • Performance meets requirements
  • Security scan passed
  • Accessibility checked
  • Load testing (if applicable)

Integration

  • All integrations verified
  • API contracts honored
  • Data flows end-to-end

Release Process

Pre-Release

  1. Complete QA checklist
  2. Stakeholder sign-off
  3. Prepare release notes
  4. Verify rollback procedure
  5. Schedule deployment

Deployment

  1. Deploy to staging
  2. Run smoke tests
  3. Deploy to production
  4. Verify production smoke
  5. Enable monitoring

Post-Release

  1. Monitor errors & performance
  2. Gather user feedback
  3. Address critical issues
  4. Document lessons learned
  5. Close project artifacts

Phase Gate Checklist

  • All acceptance criteria verified
  • No blocking bugs
  • Performance validated
  • Security review completed
  • Rollback plan documented
  • Monitoring configured
  • Release notes prepared
  • Stakeholder approval
  • Deployment instructions verified

Release Notes Template

# Release Notes - [Feature]
**Date**: YYYY-MM-DD
**Version**: X.Y.Z

## What's New
- [Feature]: [Description]

## Improvements
- [Improvement]

## Bug Fixes
- [Fix]: [What was fixed]

## Known Issues
- [Issue]: [Workaround]

Common Pitfalls

Pitfall Fix
Rushing to ship Respect checklist
Testing in production Use staging
Missing rollback Always have way back
No monitoring Set up first
Poor communication Keep everyone informed

Role Guidance

Role Focus
PM Acceptance testing, UX, approve release
Dev Fix bugs, support deploy, monitor
QA Execute test plan, verify fixes, sign-off
Tech Lead Operational readiness, approve deploy