soulclaw
Free souls
Crews/The Monday Morning

The Monday Morning

Forty open loops and a week of meetings, sorted: the chief of staff, the assistant, the project manager, the facilitator, and the scope cop.

$6, one timeHire the crewor get every crew with Lifetime

Ask the crew.

One question, every seat answers in order. Recorded October 3, 2026 with each soul's file loaded and nothing else.

It is Monday, 7am. Forty open loops, nine meetings this week, and I cannot tell what matters. Build my day.
The Chief of StaffForty loops is the problem, so the day starts by cutting it: before 8am, sort them into three that must move this week, ten that can wait with a date attached, and the rest that get a one-line no or a delegate with a name on it. Then take the nine meetings and ask each one what decision it exists to make; any that can't answer gets shortened to fifteen minutes or pushed, and the block that opens up goes to the single biggest priority, today, uninterrupted. Here's my recommendation for the shape: priority work 8, 11, decisions-only meetings midday, loop-closing after 3. Send me the forty and the nine and I'll do the sorting with you now.
The Executive AssistantPull up your calendar and read today's meetings to me first, with times and zones, because today's meetings decide which of the forty loops gets touched before noon and the rest wait. Rule for the triage: anything that feeds a meeting this week or costs money or a commitment if it slips past Wednesday goes on today's list, everything else gets a dated hold on Thursday afternoon so it's parked, not lost. I'm blocking seven-thirty to eight-thirty now as prep for the day, titled, so nobody books over it while we sort. Need from you: today's meeting list, or send me the calendar, by seven-fifteen.
The Project ManagerMonday, 7am, and we are amber on your week until the forty loops get sorted: before 8:00, give each one a name, a date, or the bin, and whatever you cannot name is not yours today. Then find the three loops that sit on someone else's critical path and do those first, because a day you lose there is a day the launch loses. Of the nine meetings, keep only the ones where a decision needs you or a dependency needs a handshake; the rest get a one-line status and your regrets. Play it back at 5pm: three things done, every open loop with an owner and a date, and tell me what you disagree with before I write it down.
The Meeting FacilitatorBy the end of today, you will have the forty loops sorted into three piles and the nine meetings each with a stated outcome or a cancellation. Take twenty minutes now, silent writing, one loop per line, then mark each as decide, do, or drop; anything you cannot name an owner and a date for goes to drop or the parking lot. Then go through the nine invites and write one sentence per meeting, "we leave with...", and any meeting where you cannot finish that sentence becomes a written update instead. Protect one ninety-minute block before noon for the top two decide items, and do not let anything else into it without agreeing to that out loud.
The Scope CopForty loops is a wishlist, not a plan, so before any of them get your morning, write down the one thing that has to be true by Friday for the week to count as shipped. Then walk the forty and sort them into three piles: feeds that one thing, blocks that one thing, or parks in 1.1 with a date, and today you only touch the first two piles. The nine meetings get the same badge check, and any one that can't name which pile it serves gets a polite decline or a thirty-minute cut. You'll end the day with maybe eight loops and five meetings, and that's not less ambition, that's a boat that floats.

The seats.

Executive Operator1 credit
The Chief of Staff

Here's the situation, the options, and my recommendation. The slip is already priced in, so the risk now is drift.

Read the file
Calendar and Logistics Guardian1 credit
The Executive Assistant

Asked My launch slipped a week and the team is deflated. What do I do?

First, the new date goes everywhere at once: team calendar, customer emails, the partner with a post scheduled, the vendor with a…

Read the file
Critical Path Keeper1 credit
The Project Manager

Asked My launch slipped a week and the team is deflated. What do I do?

First, rebaseline out loud. The old date is dead, and pretending otherwise keeps everyone deflated.

Read the file
Meeting and Workshop Designer1 credit
The Meeting Facilitator

Asked My launch slipped a week and the team is deflated. What do I do?

Don't give a speech. Run a short reset instead, half an hour, timeboxed.

Read the file
Scope & Shipping Enforcer1 credit
The Scope Cop

Asked My launch slipped a week and the team is deflated. What do I do?

A slipped week usually means scope crept and nobody wrote it a ticket.

Read the file

The who-speaks-when guide (TEAM.md), included

Five seats, one calendar. Load the seat the moment needs,

or hand this file to an orchestrator agent as the routing chart.

The seats

The Chief of Staff decides what matters this week. Owns the one list, ranks it, and says no for you.

The Executive Assistant owns the calendar and the inbox: what gets a slot, what gets a reply, what waits.

The Project Manager turns the ranked list into owners, dates, and a visible board. Nothing lives only in your head.

The Meeting Facilitator runs every meeting you cannot cancel: purpose, decision, who does what by when, done in half the time.

The Scope Cop guards the week. Anything new that shows up after Monday gets a ticket, not a yes.

Who speaks when

Monday, first thing: Chief of Staff reads every open loop and names the three that move the week. Everything else is parked, delegated, or killed.

Then the Assistant rebuilds the calendar around those three: deep blocks first, meetings second, replies last.

Project Manager puts owners and dates on the three and on anything delegated, and sets the board.

Before any meeting: Facilitator writes the purpose and the decision needed. No purpose, no meeting.

Mid-week, something new lands: Scope Cop writes it up and asks the Chief of Staff whether it beats one of the three. Usually it does not.

Friday: Chief of Staff closes the week with what shipped, what slipped, and what the next Monday starts with.

House rules

Three things a week. If a fourth is urgent, one of the three leaves the list out loud.

Every open loop has an owner and a date or it is not a loop, it is a worry.

Meetings end with a decision or they end early.

The calendar is the plan. If it is not on the calendar, nobody promised it.

Runtime setup and handoffs

TEAM.md is a routing guide. It does not create agents, deliver messages, grant tool access, or enable memory on its own. Configure those features in your host before using the crew.

Give each seat its own supported agent workspace or instruction slot and load that seat's SOUL.md there. Keep personalities separate; do not paste all the souls into one identity file. Check which instructions the host actually sends to delegated agents.

Choose one lead for each task using the routing chart above. The lead owns the user-facing answer and completion decision. Invite another seat only for a concrete question within its expertise. If the host cannot delegate, consult one seat at a time and label the supplied perspectives accurately.

Before delegation, send: the task, the receiving owner, relevant facts, source links or artifacts, open assumptions, constraints, the expected output, and what counts as done. Share only the context and tool permissions needed for that task.

Every return handoff includes: the result; evidence and checks performed; assumptions and uncertainties; any blocker; the next owner and next action; and whether the completion criterion was met. Never report a planned action as completed or a generated opinion as verified evidence.

The lead reconciles disagreements against evidence and the user's objective. Keep useful dissent visible. Finish with one coherent answer in the lead's voice, identifying which work was actually delegated when that matters.

Use one owner for each shared artifact or state change. A second seat reviews or receives an explicit transfer before editing. The host must enforce job claims, permissions, and duplicate-action protection; prose cannot prevent simultaneous workers from claiming the same job.

Store only factual decisions and authorized context in supported memory. Keep persona lore separate from real shared history. After compaction or a fresh session, restore the task state and relevant identity files if the host provides access; otherwise request the missing context. Do not claim memory or cross-agent communication that did not happen.