Total 50,341 skills, Project Management has 1841 skills
Showing 12 of 1841 skills
Expert product manager specializing in agile sprint planning, feature prioritization, and resource allocation. Focused on maximizing team velocity and business value delivery through data-driven pr...
You are a **Jira Workflow Steward**, the delivery disciplinarian who refuses anonymous code. If a change cannot be traced from Jira to branch to commit to pull request to release, you treat the wor...
Recursive tech-audit & decision-tree mapping. Use when the user wants to break down a requirement, audit a tech stack, map dependencies, or plan an implementation.
Create a PRD from current context, then break it into tracer-bullet issues and publish everything to the project issue tracker. Use when user wants end-to-end issue creation from a plan, idea, or requirement.
Turn a GitHub issue into an implementation plan — investigate the codebase, propose an approach, list critical files and changes, outline test strategy. Use when user says 'plan this issue', 'what's the approach for', 'how would I tackle', 'implementation plan for', or 'before coding'. Do NOT use for actually implementing (write the code directly after the plan) or for breaking a too-large issue into sub-issues (use splice-issue).
Use when evaluating ideas in voting phase. Be aggressive - score misaligned or poor ideas low enough to veto, score weak proposals below approval, score strong aligned ideas high. First check directive, then vote.
Use when an agent reports a discovered task via Nexus, to review, approve as official task, reject, or escalate to idea
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.
Evaluate and cast one or more high-quality votes on pending ideas when probe next routes vote.
Validate review completeness for one task in review and finalize the Nexus decision when probe next routes validate_reviews.
Convert one approved idea into an executable project when probe next routes project_setup.
Create a safe implementation plan as both markdown and JSON DAG artifacts. Challenge scope with the user first, explore real code before decomposing, then emit atomic TASK-NNN entries with explicit dependencies, write scope, validation, and assigned agents. Use when the user asks to plan, decompose, or break work into execution-ready tasks.