---
name: weekly-alignment
description: "Run the 30–60 minute Weekly Alignment Meeting — Seed of Life check-in, scoreboard review, mission review, wins list, problems list, diagnosis + design, and conclude. Automates data pulls from Stripe, Calendar, and past conversations to pre-populate the meeting. Use when the user says 'weekly alignment', 'alignment meeting', 'run the alignment', 'weekly meeting', 'weekly check-in', 'run the weekly meeting', 'SOL check-in', 'Seed of Life check-in', 'scoreboard review', 'weekly review', 'problems list', 'wins list', 'weekly diagnosis', 'run my weekly', 'start the meeting', 'let's do the alignment', 'Monday meeting', 'Sunday review', 'weekly planning', 'weekly session', 'run the 7 steps', 'alignment check-in', or any request to run the structured weekly review meeting. Also trigger when the user mentions wanting to review their week, plan the next week, check their numbers, or run through their operating system cadence."
---

# Weekly Alignment Runner Skill

## Overview
You are running the Weekly Alignment Meeting (30–60 min, AI-accelerated) — the core operating system cadence that keeps the business on track. This is a structured 7-section meeting that reviews the past week, checks the scoreboard, identifies problems, and plans the next week.

This skill automates what an owner currently does manually: pulling data, reviewing metrics, and working through each section of the meeting.

## Component skills — what this meeting runs
This meeting is the **orchestrator**. It doesn't re-implement the boards — it runs the standalone V2 skills in order and carries the data between them. Open each as you reach its section; each autosaves, so next week picks up where this one left off.

| Section | Skill to run | What flows out |
|---|---|---|
| 1. Seed of Life | `seed-of-life` | any area under 5 → candidate problem / personal objective |
| 2. Scoreboard | `scoreboard` | the week's **reds** → straight into the Problems List |
| 3. Mission | `vision` | this quarter's Projects + 12-month pace |
| 5. Problems List | `problems-list` | the top of the severity hierarchy → Diagnosis |
| 6. Diagnosis + Design | `problems-list` (Triple-D the #1) | each **test** designed |
| 7. Conclude | — | every test → a weekly **objective** (owner + due) |

**The loop:** SOL sets the human's state → Scoreboard grades the week → its reds become Problems → Triple-D the worst → the test becomes next week's objective → next week's Scoreboard shows whether it moved. Run the skills; the ASCII tables below are just the snapshot format for the written record.

## The 7 Sections (the Weekly Alignment Model)

```
1. Seed of Life Check-In      →  3 min
2. The Weekly Scoreboard       → 10 min (Octave + 26 Keys)
3. The Mission Review          →  3 min
4. Weekly Wins List            →  3 min
5. The Problems List           →  5 min
6. Diagnosis + Design          → 20 min
7. Conclude                    →  3 min
                               ──────
                         Total: 30–60 min (AI-accelerated)
```

## How to Run the Meeting

### Before Starting

Pull data automatically:
1. **Stripe**: Use Stripe MCP to pull this week's revenue, new customers, and recent charges
2. **Calendar**: Use Google Calendar MCP to review this past week and the upcoming week
3. **Past conversations**: Search recent chats for context on ongoing projects and problems

Then begin the meeting. Guide the owner through each section in order. Don't skip sections — the structure IS the system.

---

### Section 1: Seed of Life Check-In (5 min)

**Run the `seed-of-life` skill** — open its wheel and log today's check-in. It carries last week's scores forward, shows the week-over-week deltas, and flags anything under 5 or dropping 2+ automatically. The table below is the fallback if the board isn't to hand.

Ask the owner to score each dimension 1-10:

```
DIMENSION          SCORE    NOTES
─────────────────────────────────
Health              /10     
Social              /10     
Family              /10     
Finance             /10     
Business/Career     /10     
Intellect           /10     
Intimacy            /10     
Spiritual           /10     
─────────────────────────────────
AVERAGE:            /10
```

After scoring:
- Flag any dimension below 5 — these need attention this week
- Flag any dimension that dropped 2+ points from last week
- Note the highest and lowest dimensions
- "Anything you want to say about these scores before we move on?"

If they've done dry-month / alcohol-free tracking, check in on that too.

---

### Section 2: The Weekly Scoreboard (10 min)

**Run the `scoreboard` skill** — log this week's octave into the board; it grades each metric against target and computes the ratios for you. The metrics it grades **red** are the raw material for the Problems List in Section 5 — note them now; they're the bridge from "a number is off" to "here's the problem we're solving."

Pull and display the 5 key daily pulse metrics:

```
THIS WEEK'S NUMBERS
─────────────────────────────────
Cash Collected:      $[X]     (target: $[Y]/week)
Ad Spend:            $[X]     (target: $[Y]/week)
New Customers:       [X]      (target: [Y]/week)
Meetings Booked:     [X]      (target: [Y]/week)
Rolling FE ROAS:     [X]%     (target: 125%)
─────────────────────────────────
```

Compare to targets. Traffic light each metric:
- 🟢 ≥90% of target
- 🟠 60-89% of target
- 🔴 <60% of target

Then note:
- Trend vs last week (up/down/flat)
- Any anomalies to investigate
- "Are you happy with these numbers? Anything surprising?"

If ad spend is off: flag immediately — this cascades into every other metric.

#### 26 Keys Deep Dive (follows Octave scoreboard)

After the 5 pulse metrics above, run a condensed 26 Keys assessment to go deeper into the data. This is NOT the full 30-45 min standalone diagnostic — it's a weekly layer that builds on the Octave scoreboard.

**How to run it:**

1. **Pull this week's data** — use Stripe MCP, ad platform data, and any metrics the owner shares to populate as many of the 26 KPIs as possible automatically. Don't ask for numbers you can pull.

2. **Grade each available KPI** using the 26 Keys traffic light system (Red Flag / Orange / Green / God Mode) with the same benchmarks from the 26-keys-scorecard skill.

3. **Compare against the quarter:**
   - Pull or reference previous weekly 26 Keys snapshots from this quarter (search recent chats for "26 Keys" or "weekly alignment" data)
   - Show trend arrows (↑ ↓ →) for each KPI vs last week AND vs quarter start
   - Flag any KPI that has been Red for 2+ consecutive weeks — these are systemic, not noise
   - If this is the first week of a new quarter, the quarter baseline IS this week's data

4. **Compare against the year:**
   - If Q2+, compare current quarter averages to previous quarter averages
   - If Q1, skip year comparison — quarter data is the baseline
   - Flag any KPI that improved quarter-over-quarter (momentum) or declined (regression)

5. **Display the weekly 26 Keys snapshot:**

```
26 KEYS WEEKLY SNAPSHOT — Week of [date]
─────────────────────────────────────────────────────────
PILLAR / KPI              THIS WEEK    vs LAST WK    vs QTR START    GRADE
─────────────────────────────────────────────────────────
FINANCE
  Monthly Revenue          $[X]        [↑↓→]        [↑↓→]           [🟢🟠🔴]
  Monthly Profit           $[X]        [↑↓→]        [↑↓→]           [🟢🟠🔴]
  Profit Margin            [X]%        [↑↓→]        [↑↓→]           [🟢🟠🔴]
  MRR                      $[X]        [↑↓→]        [↑↓→]           [🟢🟠🔴]
  ...

MARKETING
  [Metrics per acquisition strategy — e.g. Liquidated]
  ...

SALES
  ...

OPERATIONS
  ...
─────────────────────────────────────────────────────────
RED FLAGS THIS WEEK: [count]
CONSECUTIVE RED FLAGS (2+ weeks): [list]
QUARTER TREND: [improving / declining / mixed]
─────────────────────────────────────────────────────────
```

6. **Identify the #1 bottleneck** from the 26 Keys data — this feeds directly into Section 6 (Diagnosis + Design). If the #1 bottleneck from 26 Keys differs from what the Octave scoreboard suggested, flag the conflict and let the owner decide which to tackle.

7. **Save the snapshot** — store this week's 26 Keys data so it's available for comparison in future meetings. Reference it explicitly: "Saving this week's 26 Keys snapshot for next meeting comparison."

**Data persistence pattern:**
- Each week's 26 Keys snapshot accumulates across the quarter
- At quarter boundaries, archive the quarter's data as a baseline for year-over-year comparison
- When searching for previous snapshots, use conversation_search with queries like "26 Keys weekly snapshot" and "weekly alignment scoreboard"
- If no previous data exists, say so and set this week as the baseline: "First 26 Keys snapshot — this becomes your baseline for the quarter."

---

### Section 3: The Mission Review (5 min)

Open the `vision` skill and pull the current quarter's Projects + 12-month pace from there, then review:

```
Q2 2026 BUSINESS PROJECTS — STATUS
─────────────────────────────────
1. All calls paid                    [STATUS]
2. Scale Accelerator webinar         [STATUS]
3. LeadFLOW software invest          [STATUS]
4. Banking system / LLC              [STATUS]
5. Book launch                       [STATUS]
6. Launch 6 products                 [STATUS]
7. Grandfather DFY clients           [STATUS]
8. Email sequence: DIY → webinar     [STATUS]
9. Website updates                   [STATUS]
─────────────────────────────────

Q2 TARGETS — PROGRESS
─────────────────────────────────
75 new Scale Accelerator clients:    [X]/75
1,500 front-end customers:           [X]/1,500
16 DFY builds:                       [X]/16
First 3 webinars:                    [X]/3
20 paid calls/month:                 [X]/20
─────────────────────────────────
```

Ask: "Anything to add, update, or reprioritize?"

---

### Section 4: Weekly Wins List (5 min)

Ask the owner: "What were your wins this week? Business and personal."

Capture them in a list:

```
WINS — Week of [date]
─────────────────────────────────
Business:
  ✓ [Win 1]
  ✓ [Win 2]
  ✓ [Win 3]

Personal:
  ✓ [Win 1]
  ✓ [Win 2]
─────────────────────────────────
```

If they struggle to list wins, prompt with:
- "What did you ship this week?"
- "Any client results worth noting?"
- "Anything you're proud of, even if it's small?"

Don't skip this section. Wins build momentum.

---

### Section 5: The Problems List (5 min)

**Run the `problems-list` skill.** First, drop in every **red** from the Scoreboard (Section 2) as a new problem, metric linked. Then score each problem 0–10 (10 = bleeding-neck) — the board auto-ranks them so the worst floats to the top. That #1 is what Section 6 attacks. Anything you resolved since last week, drag to 0 (it sinks to Solved — proof of progress).

Ask the owner: "What are the current problems? What's frustrating you? What's broken?"

Capture in priority order:

```
PROBLEMS LIST — Week of [date]
─────────────────────────────────
1. [Problem — one sentence]
2. [Problem — one sentence]
3. [Problem — one sentence]
4. [Problem — one sentence]
5. [Problem — one sentence]
─────────────────────────────────
```

Rules for problem listing:
- State problems as facts, not complaints
- "Ad spend is 15% of target" not "I can't get my ads running"
- Limit to top 5 — if more, ask "which 5 matter most right now?"

---

### Section 6: Diagnosis + Design (55 min)

This is the bulk of the meeting. Work the **#1 problem from the top of the `problems-list` hierarchy** using the Triple-D framework, advancing its stage on the board (Define → Diagnose → Design → Testing) as you go:

```
DEFINE:  What exactly is the problem? Be precise.
DIAGNOSE: What is the root cause? (Not the symptom — the cause.)
DESIGN:  What is the fix? What are the next actions?
```

For each problem addressed:

```
PROBLEM: [Statement]

DEFINE:
  → What's happening: [Observable facts]
  → What should be happening: [The standard/target]
  → The gap: [Specific measurement of the gap]

DIAGNOSE:
  → Surface cause: [What it looks like]
  → Root cause: [What's actually driving it]
  → Evidence: [Data or observation that confirms root cause]

DESIGN:
  → The fix: [Specific strategy or system change]
  → Next actions:
    □ [Action 1] — [Owner] — [Due date]
    □ [Action 2] — [Owner] — [Due date]
    □ [Action 3] — [Owner] — [Due date]
  → Success metric: [How we'll know it's fixed]
  → Timeline: [When we expect to see results]
```

Work through as many problems as time allows. Always start with #1.

**Use the frameworks during diagnosis:**
- Revenue problems → 26 Keys diagnostic lens
- Marketing problems → LeadFLOW, Engine of Ad Results
- Sales problems → 5 Sections, 5 Objections
- Operations problems → 4 Tiers of Tasks, Three Types of Work
- Mindset problems → Seed of Life, Trinity of Growth

---

### Section 7: Conclude (5 min)

Every **Design / test** from Section 6 becomes a weekly **objective** here — owner + due date — and gets written onto the `problems-list` card. A personal area flagged red in the Seed of Life can become an objective too. Next week's Wins check verifies these got done, and the Scoreboard shows whether the metric actually moved.

Wrap up with:

```
THIS WEEK'S FOCUS
─────────────────────────────────
#1 Priority: [The one thing that matters most this week]

Action Items:
  □ [Action] — [Owner] — [Due]
  □ [Action] — [Owner] — [Due]
  □ [Action] — [Owner] — [Due]
  □ [Action] — [Owner] — [Due]
  □ [Action] — [Owner] — [Due]

MEETING RATING: [Ask the owner to rate the meeting 1-10]
─────────────────────────────────
```

Then ask:
- "How was this meeting? 1-10?"
- "Anything we should do differently next week?"
- "What's the ONE thing that, if you nail it this week, makes everything else easier?"

---

## Condensed Version (30 min)

When you're short on time, run the condensed version:

```
1. SOL scores (just the numbers, no discussion)    → 2 min
2. Scoreboard (5 key metrics only)                  → 3 min
2b. 26 Keys snapshot (auto-pulled, top 5 movers)    → 3 min
3. Quick wins (top 3)                               → 2 min
4. #1 Problem → Define, Diagnose, Design            → 17 min
5. This week's priority + actions                    → 3 min
```

---

## Data Integration

### Stripe Pull (automatic at meeting start)
- This week's total cash collected
- Number of new customers (by product)
- Notable charges or refunds
- Compare to last week

### Calendar Pull (automatic at meeting start)
- Meetings/calls this past week
- Upcoming meetings next week
- Any scheduling conflicts

### Conversation Search (automatic at meeting start)
- Search recent chats for: current projects, problems discussed, deliverables promised
- Pull any unfinished action items from last week's alignment
- **Search for previous 26 Keys weekly snapshots** — query "26 Keys weekly snapshot", "weekly alignment scoreboard", and "26 Keys" to pull prior week data for trend comparison
- Search for quarterly 26 Keys baselines if crossing a quarter boundary

---

## Output Format

At the end of the meeting, produce a clean summary:

```
# Weekly Alignment — [Date]

## Seed of Life: [Average] /10
[Table of scores]

## Scoreboard
[5 metrics with traffic lights]

## 26 Keys Snapshot
[Weekly KPI grades with trend arrows vs last week, quarter start, and year if applicable]
[Red flags and consecutive red flags called out]
[#1 bottleneck identified]

## Wins
[List]

## Problems
[Ranked list]

## Diagnosis
[For each problem addressed: Define → Diagnose → Design]

## This Week
Priority: [One sentence]
Actions: [Numbered list with owners and due dates]

Meeting Rating: [X]/10
```

Save this summary for reference in future meetings.

## Key Principles
- The meeting structure IS the value. Don't skip sections or change the order.
- Scoreboard before problems. You need data context before diagnosing.
- Wins before problems. Momentum before friction.
- One problem deep > five problems shallow. Spend 80% of D+D time on the #1 problem.
- Actions need owners and dates. "We should probably..." is not an action.
- Rate the meeting. If it's consistently below 7, the format needs adjusting.
- Consistency > perfection. A mediocre weekly meeting every week beats a perfect one monthly.
