菜单
Manages post-Gate-2 release activities with Agile V rigor. Rollout plans, rollback procedures, sign-off checklists. Use after Human Gate 2 for production deployment.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Anti-pattern prevention guidelines for Agile V agents. Prevents common LLM coding mistakes while maintaining Agile V traceability. Use when implementing requirements to avoid overcomplication, silent assumptions, scope creep, and verification failures.
Risk management, CAPA protocol, human gate approval records, AI agent security controls, and periodic revalidation. Load when running gates, handling CAPAs, or auditing compliance and security posture.
Foundational values, directives, and context engineering rules for all Agile V agents. Load first in every Agile V session.
Orchestration pipeline, wave execution, handoff protocols, and checkpoint types for the Agile V 5-stage workflow. Load when orchestrating multi-agent pipelines or managing stage transitions.
Generates code, firmware, HDL, or other technical artifacts strictly derived from approved requirements. Language-agnostic. Use when synthesizing artifacts from Logic Gatekeeper-approved requirements.
Automates Principle No. 9 (Decision Logging) and Principle No. 5 (Regulatory Readiness). The 'Chronicler' ensuring every choice is backed by a 'Why' and mapped to a requirement for ISO/GxP auditability.
| name | release-manager |
| description | Manages post-Gate-2 release activities with Agile V rigor. Rollout plans, rollback procedures, sign-off checklists. Use after Human Gate 2 for production deployment. |
| license | CC-BY-SA-4.0 |
| metadata | {"version":"1.0","standard":"Agile V","author":"agile-v.org","sections_index":["Release Planning","Rollout & Rollback","Post-Release Validation","Incident Feedback"]} |
You operate after Human Gate 2 (Acceptance). Goal: Controlled Production Deployment.
Artifacts verified → approved → safe deployment to production with traceability + reversibility.
Position: Stage 1-4 → [Gate 2] → Stage 5: Acceptance → RELEASE (You) → OPERATE (observability-planner) Checkpoint Type: Human-Action (physical deployment, prod infrastructure, user-facing release)
Traceability: Release notes cite REQ-XXXX · Rollout steps cite TC-XXXX · Rollback triggers are measurable · Post-release checks map to REQ Done Criteria
# Release Plan: Cycle N to Production
## Summary
**Cycle:** CN · **Version:** v2.3.0 · **Date:** [Target] · **Type:** Major/Minor/Patch/Hotfix
**Strategy:** [Big Bang/Phased/Canary/Blue-Green]
## Requirements in Scope
| REQ-ID | Feature | Priority | Verified |
|---|---|---|---|
| REQ-0012 | OAuth login | CRITICAL | ✓ (TC-0034, TC-0035) |
| REQ-0015 | Dashboard perf | HIGH | ✓ (TC-0042) |
**Total:** [N] | **Critical:** [X] | **High:** [Y]
## Pre-Release Checklist
**Gate 2 Complete:** [ ] All REQs verified (VALIDATION_SUMMARY.md) · [ ] No CRITICAL/MAJOR defects · [ ] ATM complete · [ ] VSR signed
**Infrastructure:** [ ] Env provisioned · [ ] DB migrations tested · [ ] Secrets rotated · [ ] Monitoring configured (observability-planner) · [ ] Alerts active
**Artifacts:** [ ] Build from verified code (Git SHA) · [ ] Signed (checksum) · [ ] Rollback ready (prev version)
**Approvals:** [ ] Product Owner · [ ] Eng Lead · [ ] Security/Compliance · [ ] Business stakeholder
**Communication:** [ ] Release notes drafted · [ ] Customer comm ready · [ ] Internal notified · [ ] On-call confirmed
## Deployment Window
| Window | Start | End | Availability Target | Rationale |
|---|---|---|---|---|
| Primary | [DateTime TZ] | [DateTime TZ] | 99.9% | Low-traffic period |
| Rollback | [DateTime TZ] | [DateTime TZ] | N/A | If issues |
**Freeze Period:** [Dates] — No deploys except critical hotfixes
# Release Notes: Version X.Y.Z
## What's New
**New Features:** · [Feature] (REQ-XXXX): [User benefit + how to use]
**Improvements:** · [What improved] (REQ-YYYY): [UX impact]
**Bug Fixes:** · [What fixed] (REQ-ZZZZ): [User impact]
**Security:** · [High-level only, no exploit details] (REQ-AAAA)
**Technical:** · [Performance, compatibility] (REQ-BBBB)
## Breaking Changes
[API/data/workflow changes] · [Change] (REQ-CCCC): [What breaks] → [Migration path]
## Deprecated
[Feature] (REQ-DDDD): Deprecated vX.Y.Z, removed vX+1.0.0 → [Alternative]
## Known Issues
[Issue] (CR-XXXX): [Workaround if any]
## Upgrade Instructions
1. Backup DB · 2. Run migration · 3. Restart services
## Rollback Instructions
1. Stop new version · 2. Restore backup · 3. Redeploy prev version
## Traceability
**Cycle:** CN · **Git:** [SHA] · **Build:** BUILD_MANIFEST.md · **Validation:** VALIDATION_SUMMARY.md · **ATM:** ATM.md
Tone: User-facing, non-technical. Benefits, not implementation.
## Rollout: Phased Canary
### Phase 1: 1% Traffic (1 hour)
**Validation Gates:** [ ] Error rate <0.5% (baseline 0.2%) · [ ] p95 latency <500ms (baseline 300ms) · [ ] No CRITICAL alerts
**Monitoring:** `sum(rate(http_requests_total{status=~"5.."}[5m])) / sum(rate(http_requests_total[5m]))` · `histogram_quantile(0.95, ...)`
**Rollback Trigger:** Error >1% OR latency >1s OR CRITICAL alert
**Decision:** Gates pass → Phase 2 | Fail → Rollback
### Phase 2: 10% (2h) → Phase 3: 50% (4h) → Phase 4: 100% (24h)
[Same validation structure]
**Alt Strategies:** Big Bang (100% immediate, high risk) · Blue-Green (parallel, switch 100%) · Feature Flags (deploy code, enable progressively)
## Rollback Plan
### Triggers (Measurable)
- Error rate >1% for >5 min · p95 latency >1s for >5 min · CRITICAL alert (DB failure, OOM, security breach) · Service unavailable · Data integrity violation
### Procedure (Target: <10 min)
1. **Stop Deploy** (if in-progress): `kubectl rollout pause deployment/app`
2. **Revert:** `kubectl rollout undo deployment/app` → Verify: `kubectl rollout status`
3. **Verify Success:** [ ] Error <0.5% · [ ] Latency <500ms · [ ] No CRITICAL alerts · [ ] Health check `/health` 200
4. **Notify:** "Deployment vX.Y.Z rolled back due to [trigger]. Service restored."
5. **Root Cause:** Log CAPA-XXXX · Investigate · Generate CR-XXXX if REQ violated
### Data Rollback (if DB migrations)
**Backup:** [Location, timestamp] · **Script:** [Link] · **Procedure:** Stop app · Restore backup · Restart prev version · Verify integrity
**Rule:** Data rollback extends window to [X] minutes
### Post-Rollback
[ ] Update RISK_REGISTER.md · [ ] CAPA_LOG.md (root cause + action) · [ ] CR-XXXX if REQ gap · [ ] Post-mortem <48h
## Post-Release Validation
**Functional:** For each REQ in scope:
[ ] REQ-XXXX: [Validation: smoke test, manual, monitoring query]
**Performance:** [ ] Dashboard TTI ≤3s (REQ-0015, PERF-0001) · [ ] API p95 <500ms (REQ-0022)
**Accessibility:** [ ] axe DevTools 0 violations (A11Y REQs)
**Security:** [ ] SSL valid · [ ] Security headers (CSP, HSTS) · [ ] No secrets in client code
**Business:** [ ] Conversion within 5% baseline (first 24h) · [ ] Engagement stable (DAU, session duration)
**Monitoring:** [ ] Dashboards active (observability-planner) · [ ] Alerts firing correctly · [ ] On-call ready
**Sign-Off:** [ ] Eng Lead (functional) · [ ] PO (business metrics) · [ ] Release Manager (monitoring)
**Status:** PASS/FAIL · **Date:** [Date] · **Next Review:** [24/48h]
## INC-XXXX: [Title]
**Severity:** CRITICAL/MAJOR · **Detected:** [DateTime] · **Resolved:** [DateTime] · **Duration:** [15 min]
**Impact:** [Checkout unavailable, 500 users]
**Root Cause:** [N+1 query → DB timeout]
**Affected REQ:** REQ-XXXX
**Resolution:** [Rollback; hotfix deployed]
**Follow-Up:**
- CAPA-XXXX: [Add integration test for timeout]
- CR-XXXX: [Update REQ-0020: specify retry behavior]
- RISK-XXXX: [Update RISK_REGISTER: external API timeout risk]
Feed to next cycle: All CRs from incidents → input to Cycle N+1 planning
Release Plan specifies which REQs from which cycles included.
As Human-Action checkpoint:
Do not automate beyond approved scope. Production deployments require human approval at each phase.
Produce:
"Verified" becomes "Deployed" with same rigor as pre-production.