Quarter Review

If no parameter:

• Calculate current quarter based on q1_start_month
• Assume reviewing current or just-ended quarter

If parameter provided (e.g., "Q4 2025"):

• Parse quarter and year
• Review that specific quarter

Calculate:

• target_quarter: "Q1 2026"
• quarter_start: "2026-01-01"
• quarter_end: "2026-03-31"

Step 2: Context Gathering

Quarter Goals File

Check for 01-Quarter_Goals/Quarter_Goals.md:

If exists and matches target quarter:

• Extract goals that were set
• Note progress percentages (if updated)
• List milestones and completion status

If missing or wrong quarter:

• Check 07-Archives/Reviews/[quarter]-goals.md (archived version)
• If still missing: "No goals found for this quarter"

Task Completion

Scan 03-Tasks/Tasks.md for tasks completed during quarter:

• Count completed tasks in date range
• Major completions
• Tasks that were blocked

Project Activity

Scan 04-Projects/ for activity during quarter:

• Modified files in date range
• Projects launched
• Projects completed
• Projects stalled

Meetings & People

Scan 00-Inbox/Meetings/ for quarter date range:

• Total meetings held
• Key discussions and decisions
• New relationships formed

Weekly Syntheses

Look for 00-Inbox/Weekly_Synthesis_*.md files in quarter:

• Extract recurring themes
• Compile learnings
• Note energy patterns

Step 2.5: Semantic Context Enrichment (if QMD available)

Check if semantic search is available by looking for qmd in PATH.

If available, enhance the quarterly review with meaning-based analysis:

1. Link lessons to goals: For each major learning captured this quarter, search:

   qmd query "learning description" --limit 3
   

   against 01-Quarter_Goals/Quarter_Goals.md. Discover which goals a learning actually impacted, even without explicit tags.

   • Example: Learning "Realized we need better onboarding docs" semantically matches goal "Improve customer activation rate"

2. Detect hidden goal progress: For each quarterly goal, search across all meeting notes and tasks:

   qmd query "goal success criteria" --limit 5
   

   Find work that advanced the goal but wasn't explicitly linked.

   • Example: Goal "Expand EMEA presence" — QMD finds 4 meetings about European partnerships and 2 tasks about localization that were never formally linked.

3. Cross-goal connections: Search for themes that span multiple goals:

   qmd query "recurring theme from the quarter" --limit 5
   

   Surface patterns like "Customer feedback kept driving both your product and content goals."

Integration: Add a "Semantic Discoveries" subsection under each goal assessment showing work that contributed but wasn't explicitly tracked. Also add a "Cross-Goal Themes" section to the quarterly review output.

If QMD unavailable: Skip silently. Goal assessment still works from explicit data.

Step 3: Goal Assessment

For each goal from 01-Quarter_Goals/Quarter_Goals.md:

Evaluate:

• ✅ Completed: Fully achieved
• 🔄 Partial: Made significant progress but not done
• ❌ Not Started: Didn't get to it
• 🚫 Deprioritized: Intentionally stopped

For each, capture:

• What was accomplished
• What blocked progress (if incomplete)
• Key learnings

Step 4: Interactive Review

Goal-by-goal walkthrough:

"Goal 1: [Goal title]

Progress indicator showed: [X%] Milestones: [Y of Z completed]

How would you assess this goal?

• ✅ Completed
• 🔄 Partial (what % done?)
• ❌ Didn't get to it
• 🚫 Deprioritized"

Wait for user response, then:

"What happened with this goal? (Key wins, blockers, learnings)"

Capture narrative for each goal.

Overall quarter reflection:

"Stepping back, how did this quarter go?

• What were your biggest wins?
• What drained energy or didn't work?
• What would you do differently?
• What surprised you?"

Step 5: Pillar Balance Review

Read System/pillars.yaml and assess:

"Pillar balance this quarter:

• [Pillar 1]: [Goals + activity level]
• [Pillar 2]: [Goals + activity level]
• [Pillar 3]: [Goals + activity level]

Any pillar that needs more attention next quarter?"

Step 5.5: System Health & Backlog Review

Review the Dex system itself and improvement backlog.

Check Dex Backlog

Read System/Dex_Backlog.md if it exists:

Extract:

• Total ideas in backlog
• High-priority ideas (score >= 85)
• Ideas captured during this quarter
• Ideas marked as implemented

Present to user:

"Dex System Improvement Backlog:

• Total ideas captured: [count]
• High-priority (ready to implement): [count]
• Implemented this quarter: [count]

Looking at your Dex backlog:

• Any 1-2 high-impact improvements to prioritize next quarter?
• Any stale ideas (>6 months old) to archive?"

Wait for user input on:

• Which 1-2 ideas to tackle next quarter
• Any ideas to archive or refine

Suggest Backlog Review

If 3+ high-priority ideas exist:

"💡 Consider running /dex-backlog soon to re-rank ideas based on updated system state."

If no Dex_Backlog.md exists:

• Skip this section silently
• In review document, note: "Dex backlog system not yet in use"

Step 6: Generate Quarterly Review

Create 07-Archives/Reviews/[Quarter].md:

---