MCP server design, development, and audit using the Python SDK (FastMCP). Use when: creating a new MCP server, wrapping an API as MCP tools, auditing an existing MCP server for patterns and gaps, adding auth/secrets/retry/observability to an MCP server, choosing between tools vs resources vs prompts, designing MCP resources or resource templates, creating MCP prompts for workflow bootstrapping, choosing between low-level Server and FastMCP, designing tool contracts, configuring pydantic-settings, adding structured logging, writing MCP server tests, or improving an existing MCP server codebase.
Writing for specific audiences: leadership, peers, team, and org-wide. Use when: preparing an executive briefing, writing a team newsletter, communicating up/down/ laterally, announcing a launch or change, escalating an issue, delivering difficult messages, pushing back on a request, or building team visibility across the org.
OKRs and contribution goals — writing, cascading, scoring, and individual goal setting. Use when: setting team OKRs, writing individual contribution goals, cascading company OKRs to team level, coaching someone on goal quality, preparing for OKR reviews, scoring OKRs at end of cycle, or linking contribution goals to team OKRs. Covers both team-level OKRs and individual contribution goal frameworks.
Presentation design, outlining, visual best practices, and brand compliance. Use when: building a presentation outline, choosing visuals for a slide deck, structuring a talk for a specific audience, iterating on presentation content in markdown before graduating to slides, reviewing an existing deck for flow and clarity, selecting the right chart or diagram type for a given message, or ensuring slides comply with an organization's brand guide.
Communicating effectively up, down, and laterally within an org chart. Use when: preparing an executive briefing, presenting to leadership, managing stakeholder expectations, negotiating priorities with product or peer teams, escalating issues, delivering difficult messages, or building influence without authority.
Writing clear, actionable tickets in any issue tracker (Jira, Linear, GitHub Issues, ServiceNow, etc.). Use when: creating epics, stories, tasks, bugs, or spikes; writing acceptance criteria; decomposing work for a sprint; linking dependencies between tickets; auditing backlog items for clarity; or coaching a team on ticket quality. Covers title conventions, description templates, acceptance criteria, decomposition rules, dependency linking, and org-specific pluggable configuration.
>-
Rigorous critical analysis of designs, strategies, communications, and proposals. Use when: stress-testing a design or architecture, playing devil's advocate on a strategy, poking holes in assumptions, evaluating competing arguments, challenging a proposal before it ships, reviewing a communication for logical weaknesses, pressure-testing a plan before presenting to leadership, or when someone asks "what am I missing?" Works on any artifact: technical designs, business strategies, product proposals, org changes, communications, or process decisions.