Total 50,317 skills, Project Management has 1841 skills
Showing 12 of 1841 skills
Break down a change into an implementation task checklist. Trigger: When the orchestrator launches you to create or update the task breakdown for a change.
Reconcile the project's FPF state with recent repository changes
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
Use when asked to "thinking in bets", "make decisions under uncertainty", "think probabilistically", "avoid resulting", "separate decision quality from outcomes", or "reduce bias in decisions". Helps make explicit bets and evaluate decisions on process, not results. The Thinking in Bets framework (from Annie Duke) applies poker strategy to business and life decisions.
Daily standup assistant for Benjamin that compiles work priorities from Jira and Slack into a single prioritized task list. This skill should be used when Benjamin asks for morning standup, daily priorities, what to work on today, or needs to compile work items.
Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking.
Break down complex tasks into atomic, actionable goals with clear dependencies and success criteria. Use this skill when you need to plan multi-step projects, coordinate agents, or decompose complex user requests into manageable sub-tasks.
Direct research projects by gathering team feedback and delegating implementation tasks. Writes publication-quality scientific text and coordinates bioinformaticians, software developers, and biologist commentators via technical-pm.
Plan and execute organizational or technical changes. Trigger with "we're changing", "rolling out", "migration plan", "how do we communicate this change", "change management plan", or when the user is planning a change that affects people, processes, or systems.
Use this when the Discover (reverse engineering) of legacy projects tends to get out of control in coverage. You need to first conduct module classification (P0/P1/P2) and constrain the depth of reverse engineering, ensuring that high-ROI modules are made traceable first instead of "writing everything but making it unmaintainable."
Skill para estimar proyectos de software y generar documentos Word profesionales. Genera estimaciones con tiempo en meses, equipo propuesto (rol y porcentaje de dedicación), consideraciones técnicas, y warnings/riesgos. Incluye template .docx corporativo. Usar cuando el usuario pida estimar un proyecto, calcular tiempos, definir equipo necesario, generar documento de estimación, o frases como "cuánto tiempo llevaría", "qué equipo necesito", "estimar proyecto", "presupuesto de tiempo", "planificar desarrollo", "documento de estimación".
Generate and maintain changelogs following Keep a Changelog and Conventional Commits standards. Use when releasing versions, documenting changes, or updating project history.