SAIL Routine System¶
Structured routines that keep the firm's marketing, operations, and technology stack running. Each routine is a repeatable session spec that Claude can execute with minimal setup.
How to use¶
Open a Claude session and say:
"Run the Monday SEO Pulse" or "Let's do the morning briefing"
Claude reads the relevant routine spec, pulls the data it needs, and produces the expected output. For routines that propose changes (like the Google Ads War Room), nothing deploys without your Slack approval.
Daily¶
| Routine | Time | Duration | Description |
|---|---|---|---|
| Morning Briefing | Start of day | ~5 min | Status across all domains, follow-up queue, priorities |
| Google Ads War Room | Mid-morning | ~20 min | 8 specialist agents analyze and propose changes |
| Daily Content Piece | Afternoon | ~30 min | One KY personal injury content article |
Weekly¶
| Day | Routine | Description |
|---|---|---|
| Monday | SEO Pulse | GSC data, rank changes, coverage issues, action items |
| Tuesday | Google Ads Weekly Review | Campaign performance, spend analysis, strategy |
| Wednesday | Litify Health Check | Employee dashboard, intake pipeline, SMS sync |
| Thursday | Website Technical Audit | Schema, sitemap, snippets, images, redirects |
| Friday | Follow-up Queue Triage | Process 10-15 oldest "Needs Follow-up" items |
Monthly¶
| Routine | Week | Description |
|---|---|---|
| Skill Library Audit | 1st | Sync check, drift detection, retire stale skills |
| Google Ads Full Audit | 2nd | Full negative list review, consolidation |
| Content Cannibalization Review | 3rd | Thin/duplicate pages, draft cleanup |
| Litify Deep Dive | 4th | Reports, packages, knowledge center, forms |
Automated (no human trigger needed)¶
| Routine | Cadence | Description |
|---|---|---|
| Wiki Structural Refresh | Daily 10:00 UTC | GitHub Action: Notion pull + wiki compile |
| Wiki Concept Enhancement | Weekly (Sunday) | GitHub Action: Claude writes new concept articles |
Credentials¶
All routines load secrets from .credentials/vault.env.
See .credentials/README.md for setup.