Session kit · markdown

Starter: CRO

What you build

You build an executive rollup of the H2 plans of your leaders. In the session, the rollup reads the room board, because your leaders post their work there. It drafts the weekly H2 narrative and a current list of commitments and asks by owner.

The rollup can only show what the other leaders post. Early in the session, the board is thin. The full weekly rollup is a follow-up for the week after the offsite.

What you need

  • A connection to the session site, so that Claude has the see_board tool. See Connect your Claude to the session site.
  • If Claude has no connection, the text of the board page. You copy it and paste it into Claude.
  • The file h2-plan.md with your own plan. See the H2 plan template.
  • Optional: the files pipeline.csv and closed-won.csv for the full revenue team.

1. Build the view

This step gives you rung 1. The view is on rung 2 when it rebuilds from the board each time you ask. Wait until some leaders have a result on the board.

Read the room board with the see_board tool. If you do not have the tool, ask me to paste the text of the board page.
Build a table with one row for each leader. Use these columns: Leader, Function, Part of the plan, Highest rung, Results, Commitment.
Below the table, list each result by leader: the title, the kind, the rung and a summary in one line.
Use only what is on the board. Mark each gap with "NOT POSTED". Do not fill a gap with a guess.
If pipeline.csv is in the H2-Command-Center folder, add the total open Amount by Forecast Category and the export date.
State the date and the time of the board read at the top.
Save the result as h2-rollup.md. Rebuild the file from the board each time I ask.

2. Add one alert

This step gives you rung 3. The prompt holds four rules. Delete a rule that you do not want.

Add a section named "Needs me" at the top of h2-rollup.md.
Rule 1, blocked: a leader has a step with the status "blocked".
Rule 2, no result: a leader has no result on the board.
Rule 3, open ask: an ask of the business has no owner or no date.
Rule 4, same account: one account name is in the results of two leaders or more.
For each item, give the leader, the rule and the reason in one line.
Read h2-plan.md for my own asks. Read the results on the board for the asks of the other leaders.
If the board does not hold the data for a rule, tell me. Do not guess.
Run the rules now and show me what they found.

3. Add one action

This step gives you rung 4. Claude writes two drafts. You read them, you correct them and you send them.

Draft the weekly H2 narrative for my leadership team. Use h2-rollup.md and h2-plan.md.
Write four short paragraphs: where the number is, which deals decide the half, what changed this week, and what I need.
Use only facts from the board, the export and my plan. Give the source of each number.
Do not write an opinion about a named person.
Then build a list of commitments and asks by owner. For each item, give the owner, the text, the date and the status.
Add to the list at each run. Do not remove an item unless I tell you.
Save the narrative as h2-narrative.md and the list as commitments-and-asks.md.
State the date of the board read and the export date at the top of each file. Do not send a message. Only draft.

4. Schedule it

Follow the steps in Schedule it. The session site goes down after the offsite, so a scheduled task cannot read the board later. In the session, schedule the task for a time that is a few minutes from now.

Schedule a task that runs one time, ten minutes from now. The task reads the board, rebuilds h2-rollup.md, runs my four rules and updates h2-narrative.md and commitments-and-asks.md. The task states the date of the board read at the top. The task does not send a message.

For the week after the offsite, agree on one shared folder with your leaders. Each leader saves the weekly brief there. Then tell Claude to read that folder as a replacement for the board, and schedule the task for each Monday.

5. Post it

Post these results to my page. Use the same title each time, so that a new version replaces the old version.
1. Title "H2 rollup", kind "view", rung 2: the table of leaders and the date of the board read.
2. Title "H2 rollup alert", kind "alert", rung 3: the rules and what they found.
3. Title "Weekly H2 narrative draft", kind "action", rung 4: the narrative, and the number of commitments and asks by owner.
4. Title "H2 rollup schedule", kind "schedule", rung 4: what runs, when it runs, what it reads and what it writes.
State the date of the board read at the top of each result. Do not post an email address or a phone number.
Mark the steps "view", "alert", "act" and "schedule" as done.

What good looks like

  • Each number in the narrative has a source that you can open.
  • Each commitment and each ask has one owner and one date.
  • The rollup says "NOT POSTED" where a leader has no data, and it does not guess.