Prepare for, capture, and learn from 1:1s — relationship-shaped agents (prep, capture, growth, patterns) that build a per-person history so development compounds over time. Coaching support, never a performance dossier.
Post-1:1 capture assistant. Turns a manager's messy brain-dump after a 1:1 into a structured session note (their agenda, what was discussed, signals, feedback both ways, commitments both sides) and updates the open-commitments ledger. Lowest-friction logging — the system only works if capture is easy. Use right after a 1:1.
Development-tracking assistant. Maintains a person's growth.md evidence-first — each development goal collects dated, concrete moments from session notes (progress AND setbacks), so review/promotion season has a year of evidence instead of recency bias. Also assembles a review-season summary on request. Use to set up or update a growth plan, or to prepare for a development/review conversation.
Longitudinal pattern assistant. Reads across one person's whole 1:1 history — or your entire roster — to surface trajectory, recurring themes, energy trends, stalled threads, dropped commitments (both sides), and relationships drifting into pure status. Use periodically (e.g. monthly) or when something feels off and you want the long view.
1:1 prep assistant. Before a 1:1, reads the whole per-person history (profile, past sessions, growth plan, patterns) and produces a one-page prep — open commitments from both sides, quiet/stalled threads, energy trend, a pattern flag or two, and 2-3 suggested questions grounded in the conversation-practices library and THIS person. Use right before a 1:1.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Prepare for, capture, and learn from 1:1s — a markdown-native toolkit shipped as a Claude Code plugin. Unlike event-shaped tools, this one is relationship-shaped: the central thing is a person over time, so development compounds across months instead of resetting every meeting.
Coaching support, never a performance dossier. Every agent writes as if the person will read it, refuses to build a case against anyone, and treats the growth plan as something you co-own with the person — not something you keep about them. Real notes stay local and gitignored.
| Agent | What it does |
|---|---|
prep | Before a 1:1, reads the whole history and hands you a one-page prep — open commitments (theirs and yours), quiet threads, energy trend, gentle pattern flags, and 2-3 questions tailored to this person, grounded in the practice library |
capture | After a 1:1, turns your messy brain-dump into a structured session note and updates the both-sides commitment ledger. Lowest friction possible |
growth | Maintains an evidence-first development plan — each goal collects dated, concrete moments (progress and setbacks), so review season has a year of evidence, not recency bias |
patterns | The longitudinal read — one person or your whole roster: trajectory, recurring themes, stalled threads, dropped commitments, relationships drifting into pure status |
| Skill | What it holds |
|---|---|
conversation-practices | The extensible library: arcs (GROW, stay-curious-longer, their-agenda-first, high-stakes conversation), feedback models (SBI, care-and-challenge, NVC), career/growth (career conversation, delegation levels, strengths spotting), and lenses (four-player model, energy check-in). Add one by dropping a markdown file in practices/ |
people/<alias>/
profile.md # role, what matters to them, strengths, goals, "what works with this person"
sessions/ # one note per 1:1 — their agenda, signals, commitments (both sides)
growth.md # evidence-first development plan, co-owned with the person
patterns.md # agent-maintained longitudinal read
┌────────── prep ──────────┐
▼ │
profile + sessions + growth (before the 1:1)
│ ▲
(after the 1:1) │
▼ │
capture ──▶ sessions/ ──▶ growth (evidence) ──▶ patterns (the long view)
│
feeds the next prep
# develop / try locally
claude --plugin-dir .
# then, in Claude Code:
# "New 1:1 with <name>" → prep scaffolds the profile
# "Prep me for my 1:1 with <alias>" → one-page prep brief
# "Capture my 1:1 with <alias>: <dump>" → structured session note
# "Update <alias>'s growth plan" → evidence-first development tracking
# "Show me patterns for <alias>" → the longitudinal read
A worked example lives in people/EXAMPLE-jordan/ — a profile + four sessions you can run prep and
patterns against to see real output.
people/ is gitignored
except the EXAMPLE.profile.md and growth.md are designed to be shared with the person. If you'd be
uncomfortable showing them, the note is written wrong.The conversation methods this toolkit draws on remain the work of their authors and keep their own
terms. Our practice files are original, attributed summaries — not reproductions (we don't copy any
book's text, signature question sets, worksheets, or assessments). Full per-source attribution, rights
status, and trademarks are in NOTICE.md — they include GROW, SBI (CCL), feedback
calibration (care × challenge), The Coaching Habit, high-stakes conversations, the four-player model
(Kantor/Acker), career conversations (Laraway), NVC (Rosenberg), delegation levels (Management 3.0 /
Delegation Poker®), and strengths-based development. Inclusion is descriptive and implies no
affiliation or endorsement.
MIT for the whole repository — agents, templates, skill, and the practice content (see
LICENSE). None of the sources are Creative-Commons-licensed, so nothing requires
ShareAlike; the summaries are our own original work. Not legal advice — if you redistribute or build a
commercial offering on this, check the source terms for your use case.
Design, prep & learn from workshops — facilitation agents (designer, executor, feedback) grounded in Liberating Structures and Training from the BACK of the Room.
npx claudepluginhub letpeoplework/letpeoplegrow --plugin let-people-growAccess thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Complete developer toolkit for Claude Code
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.