Total 53,505 skills, Project Management has 1937 skills
Showing 12 of 1937 skills
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
Use this when you need to execute the AI SDLC (Spec Pack) process in the sdlc-dev repository, select/chain together skills from the demand side (raw/solution/prd/prototype/demo) and implementation side (plan/execute/finishing), and use guardrails to avoid context drift, incorrect directory writes, or skipping critical steps under pressure.
Guides engineering managers through the specific challenges of managing top engineers — produces a four-quadrant ability/confidence diagnostic, the Rock Star vs. Superstar distinction, common mistakes to avoid, a stagnation diagnostic (Diminishing XP), and a Pusher vs. Puller framework for managing burnout and team friction. Use when the user says "rockstar engineer," "superstar," "high performer," "brilliant jerk," "wants promotion," "hardest to manage," "overconfident," "my best developer is burning out," "engineer is frustrated," or "my best developer is pushing me." Do NOT use for standard underperformance (use performance-reviews) or general motivation questions (use engineer-motivation).
Stress-test a plan or design through structured interviewing. Use when the user wants to pressure-test a plan, resolve design decisions, or mentions "grill me".
Archive accumulated phase directories from completed milestones
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
PM orchestrator: coordinates agile and traditional PM approaches.
Diagnose GitHub-driven agile workflow problems and guide feature branch development
Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control. This skill should be used when the user asks to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wants guided step-by-step development assistance. Platform-agnostic git-only workflow without PR integration. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, merge, standup, retrospective, git.
Break an approved spec into ordered implementation tasks with dependencies, sequencing logic, and done criteria.
Prepare for PhD/Master's proposal defense — slide structure, committee Q&A simulation, proposal presentation, and defense logistics. Use when preparing to defend your research proposal before the committee.
Finish the current work Boris-style. Test it end-to-end, simplify the diff, then open a PR and stop. The PR's CI gate and the reviewer own everything after that. Use when the user says "/go", "go", or ends a request with "then go".