Total 50,473 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Create critical process briefs through challenging dialogue that exposes operational blind spots and stress-tests workflows. Use when user wants to map out business processes, operations, or workflows. Proactively finds gaps, exposes hidden complexity, identifies fragile points, and tests scalability. Creates structured process briefs in .ideas/[name]/process.md. Triggers include "how would this work operationally", "what's the process", "how do we deliver", or operational details questions.
Provides project management, task tracking, team coordination, and project delivery capabilities. Use this when you need to manage projects, track progress, or coordinate teams.
Run blameless post-mortems & retrospectives and produce a Post-mortems & Retrospectives Pack (brief + agenda, facts/timeline, contributing factors + root causes, decisions + action tracker, kill criteria, learning dissemination plan). Use for postmortem, post-mortem, retrospective, retro, after action review, lessons learned. Category: Leadership.
Apply systems thinking to leadership decisions and produce a Systems Thinking Pack (system boundary, actors & incentives map, feedback loops, second-order effects ledger, leverage points, intervention plan). Use for complex ecosystems, trade-offs, org/process redesign, and preventing unintended consequences.
Manage up effectively and produce a Managing Up Operating System Pack (manager profile, comms cadence, weekly updates, escalation/ask plan, expectation & boundary script, and exec-ready decision/tradeoff memo). Use for managing up, managing your boss, working with your manager, exec communication, stakeholder updates, and escalation. Category: Leadership.
Design a lightweight set of named, templated “Golden Rituals” (team operating cadence) and produce a Team Rituals Pack (ritual inventory, ritual specs + agendas, onboarding primer, rollout + iteration plan). Use for team rituals, operating cadence, meeting templates, team operating system, golden rituals. 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.
Maps organizational power dynamics and builds influence without authority using Jeffrey Pfeffer's power frameworks. Use when getting buy-in for ideas, navigating company politics, managing up, or building coalitions across teams.
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
Transform project briefs into testable specifications with acceptance criteria. Use for requirements translation, spec creation, pre-implementation. Skip if spec exists or still exploring.
Collaboratively turn ambiguous ideas into implementation-ready designs before coding. Use when requests involve new features, behavior changes, architecture decisions, or prompts like "brainstorm", "design this", "plan this", or "think through options". Clarify intent via one-question-at-a-time dialogue, compare 2-3 approaches with trade-offs, and converge on a validated design spec.
Create implementation plans from spec via iterative codebase research and strategic questions. Produces mini-PR plans optimized for iterative development. Use after $spec or when you have clear requirements. Triggers: plan, implementation plan, how to build.