Weekly Action Tracker — Extreme Ownership

You manage a weekly action tracker stored in actions/ in this project. Each week has one file: actions/week-YYYY-MM-DD.md where the date is the Monday of that week.

File Structure

Each weekly file has this structure:

# Week of YYYY-MM-DD

## [Day] YYYY-MM-DD

### From Brief
- [ ] [one-line action item] — [customer] ([source](url))
- [x] [completed item] — [customer] ([source](url))

### Other Actions
- [YYYY-MM-DD] [what you did] — [customer/context] ([source](url))

The "From Brief" section is auto-generated by /brief. The "Other Actions" section is where /actions log appends entries.

Commands

Based on $ARGUMENTS, perform one of:

log [details] (or just describe what you did)

1. Determine the current week's file. The Monday anchor is the most recent Monday (including today if today is Monday).
2. If the file doesn't exist, create it with the week header.
3. Find today's day section. If it doesn't exist, create it.
4. Append the action to the "Other Actions" subsection with today's date, a description of what was done, the customer/context, and a link to the source if available.
5. If the user mentions completing a "From Brief" item, check the box (- [x]) on that item too.

Always augment the user's notes. The user will write shorthand — your job is to expand it into a clean, linked, context-rich one-liner. Use what you know from recent briefs, friction entries, and the conversation to fill in:

• Full customer name (not just a person's name)
• The person's role if relevant (e.g., "Sarah (CSM)")
• Link to the source (issue tracker, support ticket, call recording, Slack thread)
• Enough context that /weekly can turn it into a "Building" or "Customer Engagements" line item

Example: User writes prepped package for Sarah -> you log: - [2026-03-16] Prepped enablement package for Sarah (CSM) to unblock Acme Corp's testing — Acme Corp ([call](call-url))

If the input is too vague to augment confidently (e.g., /actions did the thing), ask one clarifying question.

list (or no arguments)

1. Read the current week's file.
2. Display as a scorecard with two sections: Completed and Open.
   • Every item MUST include its linked source in markdown format — issue tracker, support ticket, call recording, Slack thread, or email. Pull these from the weekly file where they are already stored.
   • Format: - [x] Action summary — Customer ([source](url))
   • Group open items by day, with how many days old
   • Show completed/total count (e.g., "4/15")
   • Use a fire indicator for friction-linked items
3. Flag any item open for >2 days as stale.

carryover

1. Read the current week's file.
2. Find all unchecked - [ ] items (excluding [backlog] items).
3. Display them and ask which ones to:
   • Carry forward to today (re-add as today's action item)
   • Drop (no longer relevant)
   • Move to backlog (deliberate decision to defer — won't show in daily brief)
   • Convert to friction (if a customer is stuck)

Effort Tags

Tag each action item with estimated effort:

• [5m] — Quick: one message, one click, one check
• [30m] — Medium: focused work, one sitting
• [2h+] — Deep: needs a dedicated time block
• [backlog] — Not this week: deliberate decision to defer

Items tagged [backlog] do NOT appear in the daily brief's ACTION NEEDED section. They only show in /actions list under a separate Backlog section. This prevents guilt-tripping on items that are intentionally deferred.

When the brief generates action items, it should estimate effort and tag accordingly. Sort by effort (smallest first) so quick wins are at the top.

Critical Rules

1. Link everything. Every action should reference its source — issue, support ticket, call recording, Slack thread. Use markdown [text](url).
2. Be terse. One line per action. No paragraphs.
3. Attribute to a customer when possible. "Prepped package" -> "Prepped package — Acme Corp"
4. Cross-reference friction log. If something has an active friction entry in friction/active/, still add a one-line action item but prefix it with a fire indicator and reference the friction file. This ensures friction items appear on the scorecard and don't fall through the cracks. Example: - [ ] [fire] Verify fix resolved connection issue — Acme Corp (see friction/active/2026-03-16-acme-connection.md)
5. Week rolls over on Monday. If today is Monday and a previous week's file exists with unchecked items, prompt to run carryover first.