Total 53,748 skills, Project Management has 1951 skills
Showing 12 of 1951 skills
Technical design interview + adversarial review → living doc Technical Design section ready to implement. Stateful: detects existing sections and resumes where needed. Triggers: 'architect this,' 'how should we build,' 'design the tech,' post-define/design. Not for: scoping (explore), requirements (define), UX (design).
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. Part of the skills-for-java project
Write comprehensive commercial proposals for B2B technology consulting engagements. Integrate solution briefs, ROI/business cases, consulting pricing models (T&M, Fixed, Outcome-based, Retainer, Blended), team structure, governance, timeline, and terms. Output includes commercial-proposal.md and preliminary workplan-and-estimate.md that feeds into the PM suite's project-intake-and-charter skill. Use when creating proposals, writing SOWs, pricing engagements, or preparing commercial offers. Triggers on: proposal, commercial proposal, SOW, pricing, quote, engagement offer, commercial offer, statement of work.
Teamwork integration. Manage Organizations, Users. Use when the user wants to interact with Teamwork data.
Walk through a Jira task plan and interactively confirm assumptions, resolve open questions, and validate decisions — using progressive disclosure. Only asks questions relevant to the CURRENT phase or task being executed. Use when the user says "review the plan", "ask me questions", "clarify assumptions", "let's go through the questions", "grill me on the plan", "validate plan for PROJECT-1234", or anything about reviewing, questioning, or validating a task plan. Also triggered by the orchestrating-jira-workflow skill as Phase 3 of the pipeline, and re-invoked during Phase 5 before each task execution. Requires a task plan at docs/<TICKET_KEY>-tasks.md.
Use after exploring completes or whenever a feature already has locked requirements and now needs research, synthesis, phase definition, story mapping, and executable task beads. Use for prompts like "plan this", "break this into tasks", "decompose this work", "map the stories", "research and plan", or "turn this into beads" before implementation begins.
Nozbe Teams integration. Manage Users, Organizations. Use when the user wants to interact with Nozbe Teams data.
Set parent-child task relationship (subtask)
Recommend the next roadmap-backed change, then after explicit confirmation scaffold it as a normal spec-driven change.
Resume work from previous session with full context restoration
Apply Smith and Lewis's paradox theory to identify and manage organizational tensions across performing, organizing, belonging, and learning dimensions. Use this skill when the user needs to diagnose persistent either/or tensions, design dynamic equilibrium strategies that embrace both poles, or when they ask 'why does solving this problem make it worse', 'how do we pursue exploration AND exploitation simultaneously', or 'why do our strategic tensions keep recurring despite resolution attempts'.
Conduct stakeholder analysis using identification, Power-Interest matrix classification, and influence strategy development. Use this skill when the user needs to map stakeholders for a project, manage conflicting interests, prioritize communication, or build a stakeholder engagement plan — even if they say 'who needs to approve this', 'how do I get buy-in', or 'who might block this project'.