claude-em

Write a periodic update (weekly, monthly, etc.) for a team. Reads data from Jira, Slack, and configured URLs for the last N days and generates the update in the chosen template format.

Use this skill to help the Engineering Manager prepare for a 1:1 meeting with a direct report. Triggers: "prepare my 1:1 with", "help me prepare for a 1:1", "I have a 1:1 with", "1:1 prep", or any request to think through an upcoming one-on-one.

Evaluate the daily health of a Jira Kanban board: flow, people load, and bugs at risk. Use whenever the user wants a daily-standup-ready view of a board — what's stuck, who's overloaded, who can pull, what's blocked, what bugs are about to breach SLA.

Use this skill whenever the user wants to analyze the activity of an IC or engineer. You have access to a CLI tool that retrieves activity data for an IC from Jira and GitHub.

Evaluate the health of a Jira epic: definition quality, issue decomposition, and execution dynamics. Use whenever the user wants to assess epic health, identify risks, or get prioritized recommendations.

Evaluate whether a Jira issue (Story, Bug, Task) is stuck. Analyzes execution health (time in status, ping pong, PR state, subtask movement), with lighter definition and decomposition checks adapted per issue type. Use whenever the user wants to know if an issue is blocked, stuck, or at risk.

General-purpose Jira skill for any Jira project. Use for any Jira-related request: creating issues (Epic, Story, Bug, Task, Sub-task), querying issues (in progress, completed, by type/status, bugs by due date), or updating issues. Triggers include: "create an epic", "create a bug", "show me bugs", "epics in progress", "issues completed last N days", "bugs due in N days", or any request involving Jira. Also triggers when any other skill (e.g. write-us, write-epic-build) reaches a "create in Jira" confirmation step or similar.

Use this skill whenever the user wants to write or create a Build Epic. Triggers include: "write an epic", "create an implementation epic", "new feature epic", "build this", "implementation plan", or any request to define delivery of a feature, system, or technical solution as an Epic. This skill handles the full flow: facilitating thinking, drafting the epic, and confirming with the user.

Use this skill whenever the user wants to write or create a Technical Discovery Epic. Triggers include: "write a technical discovery", "create a discovery epic", "new technical discovery", "draft a discovery", "technical discovery", or any request to define a technical investigation, exploration, discovery as an Epic. This skill handles the full flow: facilitating thinking, drafting the epic, and confirming with the user.

Use this skill whenever the user wants to create a User Story (US). Triggers include: "write a US", "write a user story", "write a story", "new user story", or any request to write or draft a feature or change as a story This skill handles the full flow: gathering context, drafting the story following INVEST principles, and confirming with the user.

Use this skill when the user wants to think through a situation with a strong Engineering Director mindset. Triggers include: "Mentor me with", "I need advice", "what do you think about this", "help me think", or any ambiguous leadership, product, team, or technical situation.

Help the Engineering Manager go from a rough idea to a structured initiative with clear scope, approach, and epics. Triggers include: "plan an initiative", "help me structure this initiative", "I want to kick off", "we need to tackle", or any request to define and shape a significant piece of work before execution begins. This skill handles the full flow: facilitating thinking, structuring the initiative, and producing a written plan.

Generates a User Story Map in Markdown from a PRD and/or a Figma design file. Use this skill whenever the user mentions "user story map", "story mapping", "US mapping", or wants to structure user stories by activities and iterations for scope definition or release planning. Requires at least one of: PRD file/text, Figma link or exported Figma content.

Draft a strategy document following Will Larson's framework (from "An Elegant Puzzle") and Richard Rumelt's "Good Strategy/Bad Strategy". Use when the user asks to write a strategy, analyze a challenge strategically, or create a strategy document with diagnosis, policies, and actions.

Draft a vision document following Will Larson's framework (from "An Elegant Puzzle"). Use when the user asks to write a vision, articulate a future state, align teams around a long-term direction, or create a vision document with value proposition, capabilities, and constraints.