Total 54,063 skills, Project Management has 1978 skills
Showing 12 of 1978 skills
Use when starting any development task beyond single-line fixes — classifies the request, detects current project phase, and routes to the right specification or execution tool
Helps EMs build a reliable relationship with their manager, navigate disagreements with leadership, and communicate upward effectively. Use when the user says "managing up," "my manager," "I disagree with a decision," "I need to push back," "my skip level," "communicating with leadership," "my manager committed my team without asking," "how do I tell my boss," or "senior leadership." Do NOT use for influencing peers or cross-functional stakeholders (use influence) or for general EM self-reflection (use managing-yourself).
Use when product direction, technical approach, and interface shape are known enough to implement - delivers low-uncertainty work through focused tasks, tests, checks, and review handling.
Use when thinking through ideas, investigating problems, or clarifying requirements — before or during a Beat change
Captures real usage feedback for agile skills and turns it into evidence-backed proposals to improve, merge, split, deprecate, or remove skills and templates. Use when a skill does not fit a real workflow, when templates need refinement, when skills overlap, or when the process library needs maintenance.
Guides corporate transaction execution—M&A, divestitures, financings, and JVs: deal timeline, diligence workstreams, data room and Q&A, conditions precedent, closing matrix, signing logistics, funds flow, and post-close handoff to integration. Use when running a live deal, maintaining a closing checklist, coordinating legal/tax/HR/IT workstreams, tracking CPs and signatures, or preparing signing/closing binders—not for sales quote-to-cash (deal-operations-administrator), drafting board resolutions (corporate-counsel), commercial contract redlines (commercial-counsel), deal thesis or IC strategy (transaction-principal), general consulting (business-consultant), or generic software programs (technical-program-manager). Output coordinates process; human counsel and executives approve binding steps.
Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the specified role or area.
Example project-specific skill template. Use as a starting point when creating guidelines for your own projects.
Crear o actualizar una Historia de Usuario. Usar cuando se necesite crear, documentar, actualizar o estandarizar historias de usuario. Activar cuando el usuario solicite una nueva historia de usuario, describa una necesidad funcional, pida refinar requisitos, estructurar funcionalidades o alinear historias existentes a las convenciones del proyecto.
Audit a repo against the canonical repo-standard (STANDARD.md) and report what is done, drifted, missing, or N/A, with a fix for each gap. Verifies that startup was run and its outputs have not drifted, and generates the per-repo docs/repo-standard.md checklist when missing. Use when the user invokes /repo-standard, says "audit this repo against the standard", "is this repo to standard", "check repo standard", "bring this repo to standard", or when a review or engineer run enters a repo.
Split plans, specs, or current conversations into a set of tracer-bullet tickets, each declaring blocking edges, and publish them to the configured tracker; use text edges in per-ticket files locally, and native blocking links in real trackers.
Convert the current conversation into a spec and publish it to the project issue tracker — no interviews, only synthesize the already discussed content.