Skip to Content
DocumentationDeveloper GuideWorkflow

Daily Workflow

Morning

Open your terminal and start a Claude Code session in any project:

cd your-project
claude

Pick a task:

/morning

Claude fetches tasks assigned to you and shows them as a selectable list:

? What would you like to work on?
  ❯ Add team member invite flow     SGS-55 · high · linear · assigned
    Fix friction map empty state     SGS-52 · medium · linear · assigned
    Update DORA calculations         SGS-49 · low · linear · assigned
    Type something.
    Chat about this

If no tasks are assigned to you, it shows unassigned tasks from the backlog that you could pick up.

Pick one. Claude creates a git worktree in .worktrees/<task-id>/, switches into it, updates the task to “In Progress” on your ticket system, and identifies related files. Your main checkout stays on main — untouched.

Multiple Tasks in Parallel

Each task gets its own isolated worktree. You can run multiple Claude Code sessions on different tasks simultaneously:

Session 1: ~/project/.worktrees/SGS-55/   ← working on invite flow
Session 2: ~/project/.worktrees/SGS-52/   ← fixing friction map

Each session has its own branch, its own working directory, and its own task file. No conflicts.

To start a second task, open a new Claude Code session in the same project directory and run /morning again — it creates a fresh worktree for the new task.

Work

Code as you normally would with Claude Code. Tandemu collects telemetry automatically in the background — you don’t need to do anything different.

What’s tracked:

  • Session duration (start/end)
  • AI-generated vs manually written code (via Co-Authored-By commit tags)
  • Prompt loops (when you repeatedly ask Claude to fix the same issue)
  • Tool execution errors

Pause a Task

Need to switch to something urgent? Pause first:

/pause

This snapshots your progress, sends partial telemetry, and sets the task back to backlog in your ticket system. The worktree is kept so you can resume later — just open a Claude Code session in that worktree directory and run /morning.

Finish a Task

When you’re done:

/finish

Claude checks for uncommitted work:

? You have uncommitted changes. What would you like to do?
  ❯ Commit now          Stage and commit with a conventional commit message
    Stash for later     Stash changes so you can come back to them
    Leave as-is         Keep changes in working tree

Then asks about the task:

? What's the status of this task?
  ❯ Done                Task is complete — close it out and create a PR if needed
    Coming back later   Not finished yet — save progress and return to main

If done, Claude:

  1. Measures the work — cycle time, lines changed, AI vs manual ratio
  2. Sends telemetry to the OTEL collector
  3. Updates the task to “Done” on your ticket system
  4. Offers to create a PR
  5. Cleans up the worktree — removes the .worktrees/<task-id>/ directory and returns to the main checkout
  6. Shows your updated task board

Check the Team

At any point, check what’s happening across the team:

/standup

Multiple Repos

Tandemu works across repos. Your ~/.claude/tandemu.json config is global, and the task file tracks which repos you’re working in.

  1. Start a task in repo-A — /morning, pick a task (creates a worktree)
  2. Open repo-B — Claude detects you’re in a different repo and adds it to the task’s repo list
  3. Run /finish from the worktree — it measures work across all tracked repos

Task files are scoped per branch, so different tasks in different worktrees or repos never conflict.

End of Day

Everything is already tracked. Your engineering lead can see:

  • How many hours you were active
  • What tasks you worked on
  • Your AI usage ratio
  • Any friction events

No standup reports to write. No timesheets to fill. No tickets to update manually.

Last updated on
SkillsMemory