1-on-1-prep

Generates structured pre-read emails for 1-on-1 meetings with highlights, current work, and support requests.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/codewizwit/human-in-the-loop --skill 1-on-1-prep-codewizwit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 1-on-1-prep
Source: https://github.com/codewizwit/human-in-the-loop/tree/main/lib/skills/1-on-1-prep
Command: npx skills add https://github.com/codewizwit/human-in-the-loop --skill 1-on-1-prep-codewizwit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing for 1-on-1 meetings often means scrambling to recall accomplishments, project status, and blockers, resulting in unfocused meetings and missed opportunities to get support. This Skill generates a structured pre-read email so managers arrive prepared and the conversation stays productive. ## Core Features & Use Cases - Three-Section Email Structure: Produces pre-reads with highlights and wins, current work and focus, and questions or support needed, targeting 300-500 words. - Role-Aware Tone Adjustment: Adapts content depth and framing for junior engineers, senior engineers, tech leads, and engineering managers. - Optional Codebase Discovery: Reviews recent commits, PRs, and documentation to supplement user-provided project descriptions. - Use Case: A senior engineer asks for a weekly pre-read before meeting their manager and receives a markdown email covering shipped features with metrics, project status with risk indicators, and specific asks around priorities and career growth. ## Quick Start Ask the assistant to write a pre-read email for your upcoming 1-on-1 covering this week's work.

Frequently Asked Questions about 1-on-1-prep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a pre-read email for a 1-on-1 meeting?▼

Structure the email into three sections: highlights and wins with specific metrics, current work with status indicators, and questions or support needed. Keep it between 300-500 words and send it 24 hours before the meeting.

What should a 1-on-1 pre-read include for a manager?▼

Include completed work with measurable outcomes, active projects marked as on track, at risk, or blocked, and 2-5 specific asks with enough context for your manager to prepare a response. Distinguish decisions needed from input wanted.

Can the pre-read be generated from my recent commits and PRs?▼

Yes, the skill offers an optional codebase discovery mode that reviews recent git logs, PR references, and documentation updates to supplement your project descriptions with concrete work evidence.

How does the pre-read differ for junior engineers versus managers?▼

Junior engineer pre-reads focus on learning progress, training, and career path questions. Manager pre-reads emphasize team performance metrics, hiring updates, strategic planning, and escalation requests for cross-team dependencies.

What are common mistakes in 1-on-1 pre-read emails?▼

Common mistakes include writing overly long emails, hiding blockers behind only positive updates, making vague requests like "I need help", and including routine updates better suited for Slack or standups.