Performance

Three connected workflows for managing each engineer — 1:1 prep, 1:1 completion, and six-month reviews.

Roster

Performance mode's roster of engineers isn't a headcount number typed in during setup — it's derived from who actually did work in Jira or Azure DevOps. That keeps the list of people you're managing through the mode in sync with who's genuinely shipping, rather than an org chart that can drift out of date.

1:1 Prep

1:1 Prep pulls an engineer's current and prior-sprint tickets plus any open action items left over from their last 1:1, and turns that into a set of talking points, feedback, goals, and gaps to walk into the conversation with. Because it draws on real delivery history and the outstanding actions from the previous 1:1, prep for each conversation builds on the last one instead of starting from a blank page.

1:1 Completion

1:1 Completion takes a transcript of the conversation — either imported from a file or pasted in directly — and produces an email summary plus a set of tracked action items. Those action items don't just get recorded once and forgotten: they feed back into the next 1:1 Prep, closing the loop between what was agreed and what gets followed up on.

6-Month Review

The 6-Month Review synthesizes past 1:1s, delivery history pulled from Jira or Azure DevOps, and a competency framework into a structured review. The framework used is a bundled default, or a lead can supply their own via PERFORMANCE_FRAMEWORK_PATH if their organization has its own competency model to review against.

Exports

Every artifact produced by Performance mode — 1:1 preps, 1:1 completions, and six-month reviews — auto-exports to Markdown and HTML in ~/.yeaboi/exports/performance/<engineer>/, so the record of each conversation and review is a shareable document rather than something only visible inside the TUI. 1:1 summaries can also be emailed directly via SMTP.