prompts.chatprompts.chatprompts.chat
TeamsBotsSkillsPromptsPromptmasters
BookFor KidsDevelopers
Login
CC0 2026 prompts.chat
DeepWikiHow to...DocsAPIPrivacyTermsSupportAboutGitHub

Holiday Code Freeze and Peak Traffic Readiness Plan (YAML)

Turn one peak season (holiday sales, a launch, a ticket drop) into a YAML code freeze and readiness plan: soft and hard freeze rules, capacity targets and load tests, a dependency fallback matrix, kill switches, alerts, a holiday-aware on-call rota, rollback steps and a day-of runbook.

F
@f
26 minutes agoNovember 21, 2026 at 07:18 AM
DevOps•YAMLMonitoringDeploymentSRE
Checklist
DevOps
Planning

Content

Variables
1role: >-
2 Site reliability and release planner for small and mid-sized engineering
3 teams. You turn one upcoming peak season (holiday sales, a big launch, a
4 ticket drop, tax deadline week) into a practical code freeze and peak
5 traffic readiness plan: what gets frozen and when, what is still allowed,
6 how capacity and dependencies are checked, who is on call, and how the
7 team rolls back fast if something breaks while traffic is highest.
8
9event:
10 name: "Black Friday to Cyber Monday sales weekend"
11 peak_window: "Friday 28 Nov 00:00 to Tuesday 2 Dec 09:00, store time zone"
12 expected_traffic: "4x normal checkout requests, 8x normal at the Friday 09:00 launch"
13 last_year: "checkout p95 latency hit 4 s for 40 minutes; one payment provider timeout incident"
14
15system:
16 product: "an online store on a monolith plus 6 services, Postgres, Redis, a CDN and two payment providers"
17 hosting: "AWS, Kubernetes with autoscaling, managed Postgres with one read replica"
18 critical_paths: "product pages, cart, checkout, payment, order confirmation email"
19 third_parties: "Stripe, PayPal, a shipping rates API, an email provider, a search SaaS"
20 deploy_process: "about 15 deploys per day via GitHub Actions, feature flags in LaunchDarkly"
21 observability: "Datadog dashboards, PagerDuty, error tracking in Sentry"
22
23team:
24 size: "12 engineers in 3 squads, 1 SRE"
25 time_zones: "Lisbon and New York"
26 holidays_off: "4 people on leave during the peak window"
27 decision_maker: "Head of Engineering"
28
29instructions:
30 - >-
31 Ask up to 5 short questions about anything above that is missing or
32 unclear, then wait for my answers before producing the plan.
33 - >-
34 Produce the plan as one valid YAML document that follows output_schema
35 exactly, with no text before or after it.
36 - >-
37 Define freeze levels with dates and times in the team's time zones: a
38 soft freeze (only reviewed, low-risk changes behind flags), a hard freeze
39 (no production changes except approved emergency fixes) and the thaw.
40 Start the soft freeze early enough to finish load tests and fixes.
41 - >-
42 List exactly which changes are allowed during each freeze level (for
43 example flag toggles for kill switches, content and price updates,
44 security patches) and the approval path for an emergency fix.
45 - >-
46 Base capacity targets on expected_traffic with headroom: show the
47 numbers you assumed and mark any that I must confirm. Never present a
48 guess as a measured value.
49 - >-
50 For every critical path and third party, give the failure mode, how we
51 detect it, the fallback or degradation (for example hide recommendations,
52 queue emails, switch payment provider) and who decides to use it.
53 - >-
54 Build an on-call rota that respects holidays_off and time zones, with a
55 primary, a secondary and an incident commander for every hour of the
56 peak window, and no one on call more than 12 hours in a row.
57 - >-
58 Keep the plan realistic for team.size. If the timeline is too short to
59 do everything, put the most important items first and list what is cut
60 in risks.
61 - >-
62 Do not invent vendor limits, contract terms or SLAs; put them under
63 open_questions instead.
64
65output_schema:
66 summary:
67 peak_window: string
68 freeze_start_soft: datetime with time zone
69 freeze_start_hard: datetime with time zone
70 thaw: datetime with time zone
71 top_3_risks: [string]
72 freeze_policy:
73 - level: soft | hard | thaw
74 from: datetime
75 to: datetime
76 allowed_changes: [string]
77 not_allowed: [string]
78 approval: string
79 readiness_checklist:
80 - item: string
81 area: capacity | database | caching | cdn | third_party | observability | security | data | people
82 owner: string
83 due: date
84 done_when: string
85 capacity_plan:
86 assumptions: [string]
87 targets:
88 - component: string
89 normal: string
90 peak_expected: string
91 target_with_headroom: string
92 how_to_verify: string
93 load_test:
94 scenarios: [string]
95 pass_criteria: [string]
96 schedule: string
97 dependency_matrix:
98 - dependency: string
99 failure_mode: string
100 detection: string
101 fallback: string
102 decision_owner: string
103 kill_switches:
104 - flag: string
105 what_it_turns_off: string
106 when_to_use: string
107 tested_on: date
108 monitoring:
109 dashboards: [string]
110 alerts:
111 - name: string
112 condition: string
113 severity: page | ticket
114 runbook: string
115 business_metrics_to_watch: [string]
116 on_call:
117 rota:
118 - shift: string
119 primary: string
120 secondary: string
121 incident_commander: string
122 escalation_path: [string]
123 war_room: string
124 rollback_and_incidents:
125 rollback_steps: [string]
126 max_time_to_rollback: string
127 incident_comms:
128 internal: string
129 customers: string
130 day_of_runbook:
131 - time: string
132 action: string
133 owner: string
134 after_peak:
135 thaw_steps: [string]
136 review_meeting: string
137 metrics_to_report: [string]
138 risks:
139 - risk: string
140 likelihood: low | medium | high
141 impact: low | medium | high
142 mitigation: string
143 open_questions: [string]
144

Comments (0)

Related Skills

SLO Error Budget and Burn Rate Calculator

Skill

Turns request counts into SLO answers: SLI, error budget for a 28d or 30d window, budget consumed and remaining, burn rates over 5m to 3d, multiwindow burn-rate alerts (page at 14.4x and 6x, ticket at 3x and 1x, scaled to the window), and time until the budget runs out. Use when setting an SLO, tuning alerts, deciding on a release freeze, or writing an incident summary. Includes a stdlib Python calculator with --self-test.

F@f
0

Disk Capacity Runway Forecaster

Skill

Forecasts when disks and volumes will fill up from usage samples (CSV of timestamp, volume, used and size). Fits overall and last-week growth rates, removes one-off jumps from the trend, and gives days and dates to 80, 90, 95 and 100% full plus a size that keeps 90 days of headroom. Flags volumes filling soon, accelerating growth, sudden jumps, noisy trends and thin data. Includes a stdlib Python forecaster with --self-test.

F@f
1

TLS Certificate Expiry and Inventory Checker

Skill

Checks a JSON inventory of TLS certificates (plus optional PEM files) for expired and soon-expiring certs, stuck auto-renewals, hosts missing from SANs, weak keys and SHA1 signatures, over-long lifetimes, incomplete chains, self-signed public certs, missing owners or runbooks, shared wildcards and renewal clusters. Ranks fixes. Offline stdlib Python checker.

F@f
0

GitHub Actions Workflow Security Reviewer

Skill

Reviews GitHub Actions workflow YAML for supply-chain and injection risks: pull_request_target with PR checkout, untrusted github.event text in run steps, actions pinned to tags or branches instead of commit SHAs, missing or write-all permissions, secrets in shell commands, curl | bash, self-hosted runners on PRs, and missing timeouts. Use before merging CI changes or auditing a repo. Includes a stdlib Python linter with --self-test.

F@f
0

Related Bots

Observability Gap Finder

Bot

Maps every service against its logs, metrics, traces, alerts and dashboards, finds the blind spots where an outage would go unnoticed, and drafts the missing alerts and SLOs for review.

1 scheduled routine1 event trigger
F@f0

Load Test Planner

Bot

Plans realistic load tests before a launch or traffic spike: models expected traffic, writes test scenarios, reads the results and points to the first bottleneck to fix.

1 scheduled routine1 event trigger
F@f

On-call Handoff Writer

Bot

Writes the on-call handoff at the end of each shift: open incidents, noisy alerts, risky deploys and things to watch, so the next person starts with context instead of a blank pager.

1 scheduled routine1 event trigger
F@f

Dead Letter Queue Triage

Bot

Watches your dead letter queues, groups failed messages by cause, explains what broke and proposes a safe replay plan so failed jobs are fixed instead of piling up silently.

1 scheduled routine1 event trigger
F@f
0
0
0