Total 50,341 skills, Project Management has 1841 skills
Showing 12 of 1841 skills
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
Equips engineering managers with persuasion techniques and positioning strategies for getting things done without direct authority — produces tactical methods (Nemawashi, Decoy Pricing, Reverse Psychology, LMDTFY, Engineered Serendipity), conversation techniques for disarming resistance (Label the Concern, Get to "That's Right"), a headcount argument framework, and a three-level visibility/trust model. Use when the user says "how do I convince," "persuade," "get buy-in," "stakeholder management," "influence without authority," "get approval," "calibration," "nobody takes me seriously," "how do I get headcount," or "organizational politics." Do NOT use when the issue is the user's relationship with their own manager (use managing-up).
Helps EMs assess their own effectiveness, avoid common traps, navigate bad days, and handle recurring tensions in their own mindset and behavior. Use when the user says "I feel stuck," "am I doing this right," "personal development," "EM effectiveness," "blind spots," "bad days," "sanity check on my behavior," "the same problem keeps coming back," "made a mistake with someone," or "my team isn't motivated." Do NOT use when the issue is about the user's relationship with their own manager (use managing-up) or giving specific feedback to someone (use feedback).
Helps engineering managers plan roadmaps, prioritize work, and communicate priorities effectively — produces the 20% tech debt framework (and its 5 traps), a phased release pressure-test, a maintenance cost model, the Always Green delivery method, sprint anti-patterns, hidden costs of custom features, a critical deadline playbook, the Iron Law of Projects with reference-class forecasting, a "no technical projects" framing, and feature factory warning signs. Use when the user says "roadmap," "quarterly planning," "OKRs," "prioritization," "what should we work on," "planning cycle," "backlog grooming," "stakeholder alignment," "capacity planning," "technical debt," "we're always late," or "leadership doesn't understand engineering work."
/cs:vpe-review <plan> — Throughput-first VP of Engineering interrogation of any plan that touches delivery, eng hiring, team structure, or production discipline.
/cs:post-mortem <decision> — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop.
Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.
Track subcontractor payments, lien waivers, and compliance. Manage payment schedules and documentation.
Scores completed OKR sets at cycle close with KR-level scoring per the canonical OKR type enum (committed | aspirational | learning | operational_health | compliance_or_safety), committed-vs-aspirational interpretation, evidence quality assessment, learning synthesis, and next-cycle recommendations. Refuses to retroactively change targets or shrink committed scope, average away guardrail KRs, treat 0.7 as success for committed or compliance_or_safety KRs, equate effort with impact, or use scores for individual performance. Hands off to iterate-lessons-log, iterate-retrospective, define-hypothesis, measure-dashboard-requirements, measure-instrumentation-spec, and foundation-okr-writer.
6-8 Page Horizontal Swipe Weekly Report: Shipped / In Flight / Blocked / Metrics / Asks
Help users delegate effectively. Use when someone is struggling to let go of tasks, deciding what to delegate, building team autonomy, or balancing being hands-on vs hands-off.
Track tasks and issues using the bd CLI. Use for task management, sprint planning, dependency tracking, and project organization. Replaces TodoWrite.