Rain Event Contingency Card

SKILL.md

---
name: rain-event-contingency-card
description: Turn outdoor plan uncertainty into a rain contingency card with decision times, official-alert checks, backup locations, setup tasks, and guest update drafts using conservative cancellation for severe conditions.
---

# Rain Event Contingency Card

## Overview

Use this skill when outdoor plans may be affected by rain, storms, flooding, lightning, wind, or muddy conditions and the user needs a fast backup plan. The deliverable is a one-page contingency card with decision time, official weather alert checks, go/no-go thresholds, backup location, task assignments, and guest update messages.

This is a prompt-only logistics planning skill. It does not forecast weather independently, override official alerts, or encourage taking weather risks. The user should check official weather sources, venue rules, emergency management notices, transportation advisories, and local conditions. For severe weather, lightning, flooding, high winds, or official warnings, the skill should favor conservative postponement, cancellation, or moving indoors.

## Trigger

Use this skill when the user asks to:

- Build a rain plan for an outdoor party, picnic, wedding, class, sports practice, community event, market, photoshoot, yard sale, field trip, or meetup.
- Decide when to switch to a backup location.
- Draft a rain update for guests, vendors, volunteers, parents, neighbors, or participants.
- Create setup tasks for tents, indoor rooms, parking, signage, food, equipment, and communications.
- Make a conservative cancellation card for severe weather risk.

Do not use this skill to ignore official weather alerts, provide meteorological forecasting, encourage driving through flooded areas, or advise outdoor activity during dangerous conditions.

## Intake

Ask for practical details:

- Event name, date, start time, end time, timezone, and location.
- Outdoor setup details, such as lawn, park, patio, street, school field, beach, trail, market stall, or sports area.
- Expected attendance and key participants, such as children, older adults, guests with mobility needs, vendors, volunteers, or pets.
- Weather information the user has checked, especially official alerts, forecast source, expected rain window, lightning risk, wind, flood risk, heat or cold, and ground conditions.
- Backup options, such as indoor room, covered pavilion, garage, tent, nearby cafe, reschedule date, virtual option, or cancellation.
- Decision deadline, communication channels, and who must be notified.
- Non-weather constraints, such as permits, deposits, vendor cutoff times, transit, parking, accessibility, food safety, equipment, power, and cleanup.

If official weather alerts have not been checked, make that the first action item.

## Workflow

1. **Confirm the event and safety basis.** State that official weather alerts and local venue guidance should drive the decision.
2. **Set decision checkpoints.** Choose a final decision time and optional earlier watch time based on event start, vendor deadlines, travel time, and setup time.
3. **Define switch triggers.** Use user-supplied official alerts and conservative thresholds for severe conditions. Include rain intensity, lightning, flood risk, wind, unsafe travel, muddy ground, temperature, accessibility, and venue closure.
4. **Select the backup path.** Identify Plan A outdoors, Plan B indoors or covered, Plan C postpone or cancel, and the default if conditions worsen.
5. **Build the contingency card.** Include decision owner, decision time, weather source to check, location switch, supplies, setup changes, accessibility notes, and contact list.
6. **Assign setup tasks.** List who handles venue, signage, food, gear, power, seating, trash, parking, guest updates, vendors, and cleanup.
7. **Draft communications.** Provide short messages for watch notice, switch-to-backup notice, delay or postpone notice, and cancel notice. Mark drafts as review before sending.
8. **Add severe-weather rule.** If severe weather warnings, lightning, flooding, unsafe travel, high winds, or official closure occur, recommend canceling, postponing, or moving indoors rather than improvising outside.
9. **End with next actions.** Give the next three decisions or checks the user should complete manually.

## Output Format

Return these sections:

1. **Event Snapshot**: event, date, time, location, attendance, official weather source to check, and assumptions.
2. **Decision Timeline**: watch time, final call time, who decides, and notification deadline.
3. **Switch Triggers**: rain, lightning, flood, wind, venue closure, unsafe travel, ground condition, accessibility, and severe-alert triggers.
4. **Contingency Card**: Plan A, Plan B, Plan C, backup address or location details, setup changes, supplies, owner, and status.
5. **Task Board**: task, owner, deadline, materials, and notes.
6. **Guest and Vendor Update Drafts**: watch notice, backup switch, delay or postpone, and cancellation messages labeled review before sending.
7. **Accessibility and Comfort Check**: mobility, shelter, restrooms, seating, child or elder needs, pets, food safety, power, lighting, and transport.
8. **Severe Weather Safety Note**: official alerts first; conservative cancellation or indoor move for severe conditions.
9. **Next Three Actions**: the immediate manual checks or decisions.

For an urgent request, start with Decision Timeline, Switch Triggers, and the message draft.

## Planning Rules

- Prioritize official weather alerts, venue notices, emergency management guidance, and local safety instructions over convenience.
- Do not invent current weather, active alerts, venue policies, road closures, or forecast details.
- If the user has not supplied official alert status, list checking official alerts as the first action.
- Use conservative triggers for severe conditions, including lightning, flooding, official warnings, high wind, unsafe travel, or venue closure.
- Consider setup and teardown time, vendor cutoffs, guest travel, accessibility, children, older adults, pets, electrical equipment, food safety, and muddy ground.
- Keep communication drafts short, clear, and easy to send manually.

## Boundary Rules

- Do not provide independent weather forecasting or claim to have checked live alerts unless a permitted web or official-source lookup was actually performed in the current task.
- Do not encourage outdoor continuation during severe weather warnings, lightning, flooding, high winds, unsafe travel, or official closures.
- Do not advise driving, walking, biking, or transporting equipment through flooded or unsafe areas.
- Do not send messages, contact vendors, change reservations, or cancel bookings unless the user separately authorizes that external action.
- When safety and convenience conflict, recommend the safer indoor, postponement, or cancellation option.

## Acceptance Criteria

1. Produces a rain contingency card with decision timeline, switch triggers, backup path, task board, and update drafts.
2. Uses official weather alerts and local venue guidance as the decision basis when supplied, and prompts the user to check them when missing.
3. Recommends conservative cancellation, postponement, or indoor move for severe conditions.
4. Does not invent weather data, live alerts, venue policies, closures, or road conditions.
5. Provides guest or vendor messages only as review-before-sending drafts unless separately authorized.
6. Requires no code execution, credentials, API access, network access, booking changes, outgoing messages, or extra files.

## Example Prompts

- "My picnic may get rained out tomorrow. Make a backup plan and guest text."
- "Build a rain contingency card for an outdoor birthday party."
- "We have a market booth and storms are possible. Help me decide switch triggers."
- "Make a conservative cancellation plan for a field day if there is lightning."
- "Draft a message moving guests from the park to our indoor backup."