Browse / Software development / engineering-manager-tools

engineering-manager-tools

pavelbely

Claude Code workspace for engineering managers: /add1, /sync-1-1s and /week-rollover for running 1-1s.

Open pavelbely/engineering-manager-tools → Manually confirmed as a workspace.

Built for Claude Code

ships .claude CLAUDE.md and nothing for other agents.

In its own words

Aboutpavelbely/engineering-manager-tools

Ships with mock data.

README.md

A Claude Code workspace for running 1-1s as an engineering manager — three slash commands plus the file layout they operate on.

Everything here is mock data. The company, the product and all four engineers are made up, so you can clone it, run the commands, and watch them work before pointing anything at your real notes.

Videos

Full series: Claude Code for Engineering Managers

  • Claude Code for Engineering Managers (Getting Things Done) — now.md / then.md / someday.md and /week-rollover
  • Run 1-1 with your team using Claude Code — the 1-1 folder layout, /add1 and /sync-1-1s

More short clips on using AI as a manager: AI for Managers

The commands

They live in .claude/commands/. The prompts are the whole implementation — there's no code to install.

Try it

/sync-1-1s defaults to provider: "mock", which reads .claude/mock-fathom-inbox/. Nothing leaves your machine and no API key is needed.

Making it yours

  • Rewrite CLAUDE.md — your company, your product, your team table.
  • Replace the team array in .claude/1-1-sync.config.json with your own people:

name, slug (must match the folder under 1-1s/), aliases used in meeting titles, and the weekly slot that /add1 uses to work out the next 1-1.

  • Rename the folders under 1-1s/ to match those slugs, and empty out the mock content.
  • Point provider at a real recording source:

API keys are read from environment variables and are never stored in the repo.

The repository's own description, then 78% of its README. Read the rest on GitHub ↗

Read from the repository's git tree on 2026-08-17.