Total 54,003 skills, Project Management has 1964 skills
Showing 12 of 1964 skills
Build or refresh a team culture and produce a Team Culture Operating System Pack (culture snapshot, culture code, norms, rituals, rollout + measurement plan). Use for team culture, culture code, team values, team norms, psychological safety, and coaching culture. Category: Hiring & Teams.
Writes effective OKRs using Christina Wodtke's best practices and Google's OKR methodology. Use when setting goals, aligning teams, creating measurement frameworks, or tracking quarterly progress.
Reviews feature specifications for completeness, testability, and implementation readiness. Validates acceptance criteria, edge cases, and technical constraints. Use when reviewing feature specs before implementation or during sprint planning.
Transform project briefs into testable specifications with acceptance criteria. Use for requirements translation, spec creation, pre-implementation. Skip if spec exists or still exploring.
Create or update `tasks/todo.md` as the prioritised project backlog with clear `feat`/`fix`/`chore` items and ordering. Triggers: new backlog, update todo.md, add backlog item, reprioritise roadmap.
Analyze and compare construction bids, proposals, estimates, and subcontractor quotes. Assigns line items to UniFormat II headings, compares absolute cost and cost per unit, produces a leveling spreadsheet (CSV or Excel) and a concise PDF report with scope overlap matrix, contractual term comparison, and a recommendation. Use when the user provides one or more bid documents (PDFs, spreadsheets, or text) to analyze or compare, or asks to "level bids", "compare bids", "bid tabulation", "bid comparison", "bid analysis", or "analyze this bid/quote/proposal" for a construction project.
Use when identifying launch risks, mitigation plans, and escalation owners.
Use when planning work (to create items and tasks), when starting implementation (to mark tasks in-progress), when completing work (to mark tasks done), or to check backlog status. Manages .backlogmd/ for features, bugfixes, refactors, and chores.
Devil's advocate. Seek contrary evidence before locking in. Use when about to make a significant decision, when confidence is high but stakes are higher, or when the team is converging too quickly.
Closure & Learning (The Learner): Formalize project closure, capture lessons learned, and generate final reports.
Use when making high-stakes decisions under uncertainty that require stakeholder buy-in. Invoke when evaluating strategic options (build vs buy, market entry, resource allocation), quantifying tradeoffs with uncertain outcomes, justifying investments with expected value analysis, pitching recommendations to decision-makers, or creating business cases with cost-benefit estimates. Use when user mentions "should we", "ROI analysis", "make a case for", "evaluate options", "expected value", "justify decision", or needs to combine estimation, decision analysis, and persuasive communication.
Master hiring processes, interviewing, candidate assessment, and building strong engineering teams