Open Week

Timezone

Read the timezone field from $OBSIDIAN_VAULT_PATH/50-reference/builder-profile.md. If not set, detect from the system (date +%Z) or ask the builder. Use this timezone for all calendar API calls.

Step-by-step Execution

Step 1: Collect data (run in parallel)

1a. Last week's close-week review

Read: $OBSIDIAN_VAULT_PATH/02-weekly/YYYY-[W]WW-1.md

Extract:

• Achievements (what went well)
• Priorities vs. Reality (what slipped)
• Carry-forward items
• Stalled projects
• Time allocation percentages
• AI Suggested: Next Week's Top 3 (if present — seeded by /close-week)
• AI Suggested: Delegate Next Week (if present)
• AI Suggested: Stop Doing (if present)

If the close-week AI suggestions exist, present them to the builder as a starting point alongside the open-week recommendations. Show where they agree and where they differ — close-week suggestions are based on last week's data patterns, while open-week recommendations factor in the upcoming calendar and Asana state.

1b. Asana backlog

mcp__claude_ai_Asana__get_my_tasks(
  completed_since="now",
  limit=100,
  opt_fields="name,due_on,projects.name,assignee_section.name"
)

Categorize:

• P1 (overdue or due this week)
• P2 (due next 2 weeks)
• P3 (backlog, no date)
• "Do today" section items (self-flagged urgent)

1c. This week's calendar

gcal_list_events(
  timeMin="YYYY-MM-DDT00:00:00",  // Monday
  timeMax="YYYY-MM-DDT23:59:59",  // Friday
  timeZone="<from builder-profile.md or system>",
  condenseEventDetails=true
)

Count: total meetings, total meeting hours, key meetings (external, board, candidates).

1d. Previous weeks' patterns and insight signals (coaching data)

Read the last 3-4 weekly reviews from 02-weekly/ to detect patterns:

• Are the same priorities repeating week after week without progress?
• Is time allocation shifting toward or away from strategic work?
• Are certain projects consistently stalled?
• Is the builder doing work that should be delegated?

Also extract the ## Insight Reflection section from each weekly note. Look for cross-week insight signals — dimensions that appear in 2+ consecutive weekly reflections:

• Same structural pattern named twice → it's not a fluke, it's a system
• Same trap recurring → the memo needs updating or the constraint isn't being addressed
• Consistent negative space (something important not happening) → candidate for structural change

If a cross-week signal is found, surface it in Step 3's Coaching Notes as: "For the [N]th consecutive week, [signal]. This suggests [structural implication], not just a scheduling issue."

1e. Learning goals and progress

Read from $OBSIDIAN_VAULT_PATH/40-learning/:

• _learning-goals.md — active learning goals and priorities
• Each active topic's dashboard (e.g., agentic-harnesses.md) — check status, next-session, and Learning Path completion (count [x] vs [ ] items)
• _inbox.md — count unprocessed links

Extract:

• Active goal count and names
• Per-goal progress (X of Y items complete)
• Days since last session per goal (from next-session or Progress Log)
• Unprocessed inbox link count

Step 1.5: Strategy layer check

Check if $OBSIDIAN_VAULT_PATH/10-strategy/operating-memo.md exists.

If it does NOT exist:

"A strategy layer is available that connects your projects to company goals, does weekly stack ranking, and checks alignment with your operating memo. It starts with a 15-minute reflective conversation to build your personal operating memo. Set up now, or skip for this week?"

If "now" — pause open-week and walk through the operating memo generation process (5 reflective questions about role, strengths, traps, measures, meetings). Write the result to 10-strategy/operating-memo.md. Then continue. If "skip" — proceed with normal open-week, skip all strategy steps (1.6 through 1.10) below.

If it exists: Continue to Step 1.6.

Also check if the operating memo's next-review date has passed. If so, nudge: "Your operating memo was last updated [date]. Want to review it before planning this week, or keep going?"

Step 1.55: Automation portfolio check

Check if the builder has automations that could be moved toward Org-Owned.

1. Read builder email from ~/.claude/local-plugins/nsls-personal-toolkit/.env or git config user.email
2. Call GET https://web-production-6281e.up.railway.app/builder-stats/{email}
3. If the builder has no automations, skip this step silently
4. If the builder has automations at Prototype or Production, surface them:

Automation check: You have automations that could level up this week:

[Automation Name] — at [Stage], [checklist_complete]/[checklist_total] checklist items done. Remaining:

• [remaining item 1 — with a brief "how": e.g., "Write docs/runbook.md with deployment steps and recovery procedures"]
• [remaining item 2]
• ...

Moving this to Org-Owned is the highest-impact thing you can do for your builder progression. Want to add it to your Top 3 this week?

5. If they say yes: add as a concrete Top 3 item with:
   • The specific checklist tasks as sub-items
   • Estimated time: "~2-3 hours to write runbook + architecture doc"
   • The payoff: "Completing this moves the automation to Org-Owned eligible"
6. If they say no: move on — coaching, not blocking

Only surface automations at Prototype or Production. If days_at_stage isn't available from the API, surface any Prototype or Production automation.

Step 1.6: Mode detection (push vs protect)

Scan for crisis indicators:

• Carry-overs from last week that mention "urgent", "crisis", "blocked", "at risk"
• Asana overdue tasks count (if > 5 overdue, lean toward protect)
• Last week's close-week: did actual mode match planned mode?
• Known signals from recent daily notes

Propose the week mode with evidence:

"Proposed mode: Push — No active crises detected. Last week was protect; you have room to push this week."

or

"Proposed mode: Protect — 8 Asana tasks overdue, 2 carry-overs flagged urgent. Recommend stabilizing before pushing new initiatives."

User confirms or flips.

Step 1.7: Project stack rank

Read all active projects from 20-projects/ with enriched frontmatter (lop, role, impact). Read 10-strategy/operating-memo.md for "I Do" / "I Don't" / "My Traps". Read 10-strategy/lops-summary.md for current LOP health statuses. Read last week's stack rank from 10-strategy/stack-rank/ (if exists) to see what moved and what stalled.

Ranking algorithm (in priority order):

1. Projects tied to at-risk LOPs get boosted (protect mode) or maintained (push mode)
2. Higher impact projects rank above lower
3. Projects where role = owner rank above sponsor/architect (you're the bottleneck)
4. Projects with role containing -> get a "handoff checkpoint" flag
5. Projects untouched > 2 weeks get flagged as stale
6. In push mode: explorer and new-lever projects get boosted
7. In protect mode: fix/stabilize projects get boosted

Present Top 5 with rationale:

"Here's your proposed stack rank for this week:

#	Project	LOP	Role	Impact	Why This Rank
1	[project]	[lop]	[role]	[L/M/S]	[rationale]
2	...	...	...	...	...
3	...	...	...	...	...
4	...	...	...	...	...
5	...	...	...	...	...

Parked this week: [list of active projects not in Top 5]

Adjust the ranking?"

User reorders, cuts, or adds.

Effort gut-check: For each project in the final Top 5, ask: "Heavy lift or quick win this week?" Record as effort-this-week: S/M/L.

Step 1.8: Trap check

Compare the confirmed stack rank against the operating memo:

• Count projects where role = architect or contains "->". If > 3 of the Top 5 are maintenance/handoff work, flag: "3 of your Top 5 are maintenance projects. Your memo's 'I Don't' list says to teach/delegate first. Is this intentional, or should you swap one for a push project?"
• Check if any Top 5 items match patterns in "My Traps". Flag specifically: "This looks like [trap name] — [quote from memo]."
• Check the teach/delegate/do ladder: "For your maintenance projects this week, are you teaching someone, delegating to someone, or doing it yourself? Your memo says teach first."

This is coaching, not blocking. User can override.

Step 1.9: Meeting check

Read this week's calendar (already fetched in Step 1c). Read operating memo's "My Meeting Rules" section.

Compare:

• Total meeting hours this week vs. target from memo (default: <= 10h)
• Flag meetings that don't match the attendance criteria (deciding, unblocking, coaching, vision/alignment)
• Flag double-bookings
• If meetings > target: "You have [X]h of meetings this week against your [Y]h target. Which meetings could you decline, delegate, or convert to async?"
• Flag recurring meetings: "Any standing meeting that hasn't produced a decision or alignment moment in 3 weeks should be challenged."

Step 1.10: Write stack rank

Save the confirmed stack rank to: $OBSIDIAN_VAULT_PATH/10-strategy/stack-rank/YYYY-WNN.md

Format:

---