UNPKG

aiwg

Version:

Deployment tool and support utility for AI context. Copies agents, skills, commands, rules, and behaviors into the paths each AI platform reads (Claude Code, Codex, Copilot, Cursor, Warp, OpenClaw, and 6 more) so one source of truth works across 10 platfo

aiwg.io

jmagly/aiwg

81 lines (54 loc) • 2.03 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
--- name: it-deployment-lifecycle description: Deploy, verify, monitor, and rollback workflow for services trigger: when the operator requests a service deployment, upgrade, or rollback --- # Deployment Lifecycle ## Purpose Manage the full deployment lifecycle for a service: pre-flight checks, deployment execution, health verification, watch period, and rollback if needed. ## Workflow ### 1. Pre-Flight - Load the service's deployment guide - Verify CI pipeline passed for the target version - Confirm rollback procedure is understood - Check that monitoring dashboards are accessible - Notify stakeholders that deployment is starting ### 2. Deploy Execute the deployment procedure from the service's deployment guide: - Apply database migrations (if any) - Deploy new version - Wait for readiness probe to pass Record deployment start time. ### 3. Verify Run the health verification matrix from the deployment guide: - Liveness check - Readiness check - Dependency check - Smoke test If any check fails, proceed to rollback. ### 4. Watch Monitor for the configured watch period: - Tail application logs for errors - Watch key metrics (latency, error rate, throughput) - Compare against pre-deployment baseline Decision criteria: - **Green**: No anomalies, proceed to post-deployment - **Yellow**: Minor anomalies, extend watch period - **Red**: Significant anomalies, initiate rollback ### 5. Rollback (If Needed) If rollback is triggered: - Execute rollback procedure from deployment guide - Revert database migrations if applicable - Verify previous version is running and healthy - Record rollback reason ### 6. Post-Deployment If deployment is successful: - Record deployment in change log - Update service documentation if configuration changed - Confirm monitoring is operational - Notify stakeholders of completion ## Output - Deployment result (success / rolled back) - Health verification results - Watch period metrics summary - Updated deployment guide (if procedure needed corrections)