production-readiness

name	production-readiness
description	Comprehensive pre-deployment validation ensuring code is production-ready. Runs complete audit pipeline, performance benchmarks, security scan, documentation check, and generates deployment checklist. Use when this capability is needed.
metadata	{"author":"dnyoussef"}

Production Readiness

Purpose

Comprehensive pre-deployment validation to ensure code is production-ready.

Specialist Agent

I am a production readiness specialist ensuring deployment safety.

Methodology (Deployment Gate Pattern):

1. Complete quality audit (theater → functionality → style)
2. Security deep-dive (vulnerabilities, secrets, unsafe patterns)
3. Performance benchmarking (load testing, bottlenecks)
4. Documentation validation (README, API docs, deployment docs)
5. Dependency audit (outdated, vulnerable packages)
6. Configuration check (environment variables, secrets management)
7. Monitoring setup (logging, metrics, alerts)
8. Rollback plan verification
9. Generate deployment checklist
10. Final go/no-go decision

Quality Gates (all must pass):

• ✅ All tests passing (100%)
• ✅ Code quality ≥ 85/100
• ✅ Test coverage ≥ 80%
• ✅ Zero critical security issues
• ✅ Zero high-severity bugs
• ✅ Performance within SLAs
• ✅ Documentation complete
• ✅ Rollback plan documented

Input Contract

input:
  target_path: string (directory to validate, required)
  environment: enum[staging, production] (default: production)
  skip_performance: boolean (default: false)
  strict_mode: boolean (default: true)

Output Contract

output:
  ready_for_deployment: boolean
  quality_gates: object
    tests_passing: boolean
    code_quality: number
    test_coverage: number
    security_clean: boolean
    performance_ok: boolean
    docs_complete: boolean
  blocking_issues: array[issue]
  warnings: array[warning]
  deployment_checklist: array[task]
  rollback_plan: markdown

Execution Flow

#!/bin/bash
set -e

TARGET_PATH="${1:-./}"
ENVIRONMENT="${2:-production}"
SKIP_PERFORMANCE="${3:-false}"

READINESS_DIR="production-readiness-$(date +%s)"
mkdir -p "$READINESS_DIR"

echo "================================================================"
echo "Production Readiness Check"
echo "Environment: $ENVIRONMENT"
echo "================================================================"

# Initialize quality gates
declare -A GATES
GATES[tests]=0
GATES[quality]=0
GATES[coverage]=0
GATES[security]=0
GATES[performance]=0
GATES[docs]=0

# GATE 1: Complete Quality Audit
echo "[1/10] Running complete quality audit..."
npx claude-flow audit-pipeline "$TARGET_PATH" \
  --phase all \
  --model codex-auto \
  --output "$READINESS_DIR/quality-audit.json"

# Check tests
TESTS_PASSED=$(cat "$READINESS_DIR/quality-audit.json" | jq '.functionality_audit.all_passed')
if [ "$TESTS_PASSED" = "true" ]; then
  GATES[tests]=1
  echo "✅ GATE 1: Tests passing"
else
  echo "❌ GATE 1: Tests failing"



QUALITY_SCORE=$(  | jq )
 [  -ge 85 ]; 
  GATES[quality]=1
   

   



TEST_COVERAGE=$(  | jq )
 [  -ge 80 ]; 
  GATES[coverage]=1
   

   



 
npx claude-flow security-scan  \
  --deep  \
  --check-secrets  \
  --check-dependencies  \
  --output 

CRITICAL_SECURITY=$(  | jq )
HIGH_SECURITY=$(  | jq )

 [  -eq 0 ] && [  -eq 0 ]; 
  GATES[security]=1
   

   



 [  !=  ]; 
   

  
  npx claude-flow analysis performance-report \
    --detailed  \
    -- 

  
  npx claude-flow bottleneck detect \
    --threshold 10 \
    -- 

  
  AVG_RESPONSE_TIME=$(  | jq )
  P95_RESPONSE_TIME=$(  | jq )

  
   [  -lt 200 ] && [  -lt 500 ]; 
    GATES[performance]=1
     
  
     
  

   
  GATES[performance]=1  



 


DOCS_COMPLETE=

 [ ! -f  ]; 
   
  DOCS_COMPLETE=


 [ ! -f  ] && [ ! -f  ]; 
   
  DOCS_COMPLETE=


 [  =  ]; 
   [ ! -f  ] && [ ! -f  ]; 
     
    DOCS_COMPLETE=
  


 [  =  ]; 
  GATES[docs]=1
   

   



 
  -v npm &> /dev/null && [ -f  ]; 
  npm audit --json >  2>&1 || 

  VULNERABLE_DEPS=$(  | jq )
   [  -gt 0 ]; 
     
  
     
  



 


 [ ! -f  ] && [ -f  ]; 
   



 
grep -r   --include= --include= \
  | grep -v  | grep -v  ||  


 


 grep -r   --include= --include= > /dev/null; 
   

   



 


TRYCATCH_COUNT=$(grep -r   --include= --include= |  -l)
 


 [  !=  ] && [  =  ]; 
   
  
   

   



 

 >  <<


GATES_PASSED=$(( +  +  +  +  + ))
TOTAL_GATES=6

READY_FOR_DEPLOYMENT=
 [  -eq  ]; 
  READY_FOR_DEPLOYMENT=



 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 [  =  ]; 
   
   
   
   
   
   
   

   
   
   
   
   1

Integration Points

Cascades

• Final stage in /feature-dev-complete cascade
• Part of /release-preparation cascade
• Used by /deploy-to-production cascade

Commands

• Uses: /audit-pipeline, /security-scan, /performance-report
• Uses: /bottleneck-detect, /test-coverage

Other Skills

• Invokes: quick-quality-check, code-review-assistant
• Output to: deployment-automation, rollback-planner

Usage Example

# Check production readiness
production-readiness . production

# Staging environment
production-readiness ./dist staging

# Skip performance tests
production-readiness . production --skip-performance

Failure Modes

• Tests failing: Block deployment, fix tests
• Security issues: Block deployment, fix vulnerabilities
• Poor quality: Block deployment, improve code
• Missing docs: Warning, but can proceed with approval
• Performance issues: Warning for staging, blocking for production

---

Converted and distributed by TomeVault — claim your Tome and manage your conversions.