Pace
← All cookbooks Productivity cookbook

Productivity

The cross-role utility belt: managers writing status updates, ICs assembling end-of-day recaps, founders searching for the decision they made three sprints ago. Install regardless of role; pair with whichever team plugin you already use.

Marquee recipe

Daily update that pulls itself together

Async standups stop being a chore.

Trigger
Routine, schedule, weekdays 17:30
Skills
update, task-management
Features
Routines (cloud schedule), Slack + Notion + Linear connectors, plan mode

End of the day, the routine assembles what you shipped (commits, tickets closed, Slack threads contributed to) and drafts a one-paragraph wrap; rolls open work into tomorrow's queue. Plan mode parks the draft for your edit before it posts to your team's standup channel. Async standups stop being a chore.

How to set it up

  1. 1
    Install the productivity plugin
    Install in Cowork ↗ claude plugin install productivity@pace
  2. 2
    Authorize Slack, Linear, Notion, and GitHub

    Whatever subset you use. The skill pulls signals from each, so the more sources connected the richer the wrap.

  3. 3
    Create the scheduled routine

    In Cowork, open Routines → New routine → Schedule · Weekdays · 17:30.

  4. 4
    Paste this as the routine prompt

    Edit the channel + role-focus line to match your team.

    Routine prompt 
    End of day check-in. Run update to assemble
what I shipped today: commits merged, Linear tickets I
moved, Slack threads I contributed substantively to, docs
I edited in Notion.

Then run task-management to roll my open
items into tomorrow's queue (carry forward unchecked
todos, surface things I said I'd do but haven't).

Draft a 3-line async standup post in our voice:
"Yesterday I... Today I will... Blockers: ..."

Use plan mode : show me the draft for a quick edit
before posting to #async-standup.
  5. 5
    Click Run now to verify

    The first run today shows you the draft format. Plan mode means you approve before it posts. Tomorrow at 17:30 it runs again automatically : you'll get a notification in the Claude app when the draft is ready for your edit.

Project memory that follows you across sessions

Trigger
Interactive, when starting work after a break
Skills
memory-management, start
Features
Auto memory (CLAUDE.md), cross-app context retrieval

start re-hydrates yesterday's context from memory-management: open threads, the decisions you made, the things you said you'd come back to. No more spending the first 20 minutes of every session reading old messages.

How to use it

  1. 1
    Ready to use

    No routine to configure for this one. Just open Cowork (or Claude Code) and paste the prompt below.

  2. 2
    Try it with this prompt
    Project memory prompt 
    I need to find: [what we decided about pricing in the Q3 launch retro].

Search across Slack channel histories (#product, #pricing, #leadership), Notion docs, Linear comments, and GitHub PR discussion. Surface the actual decision (not just the discussion), with the date it was made and a link back to the source.

End-of-week recap, written for you

Trigger
Routine, schedule, weekly Friday 17:00
Skills
update, tasks
Features
Routines (cloud schedule), Linear + GitHub + calendar connectors, multi-source pull

Pulls what you shipped, what you reviewed, what you started, and what slipped. Drafts the recap email or status update in your voice, ready to send (or skip) on Monday. Trains itself on your past updates after a few weeks so the tone matches.

Weekly recap prompt 
Every Friday at 5pm, pull what I shipped this week (Linear closed, GitHub merged), what I reviewed (PRs I commented on), what I started (branches created), and what slipped (carryover from last week's plan).

Draft my recap email in my voice, ready to send Monday morning. Match the tone of recent recaps I've sent (read the last three from my sent folder).

Park the draft in Notion under /personal/recaps so I can edit before sending.

Project memory: search across every decision your team made

Ask "what did we decide about pricing in the Q3 launch retro?" and Claude searches across Slack, Notion, Linear comments, and GitHub PR threads simultaneously, surfaces the actual decision (not just the discussion), and links back to source. The work of remembering moves from you to the agent.

Trigger
Cowork chat, on demand
Skills
memory-search, synthesize
Features
Cowork chat, multi-source connectors (Slack + Notion + Linear + GitHub), enterprise-search pairing

How to set it up

  1. 1
    Create the Cowork hook

    In Cowork, open Hooks → New hook. Match the trigger described above (file upload, message, schedule).

  2. 2
    Paste this as the routine prompt
    Project memory prompt 
    I need to find: [what we decided about pricing in the Q3 launch retro].

Search across Slack channel histories (#product, #pricing, #leadership), Notion docs, Linear comments, and GitHub PR discussion. Surface the actual decision (not just the discussion), with the date it was made and a link back to the source.
  3. 3
    Click Run now to verify

    Eyeball the first run for accuracy. Once it looks right, the routine fires on its trigger from then on. Assumes the plugin from the marquee above is already installed and connectors authorized.