Total 30,743 skills, Project Management has 1152 skills
Showing 12 of 1152 skills
Requirements Analysis SKILL, which can further interact with users to clarify requirements
Requirements Review SKILL, which can further interact with users to clarify requirements
Creates structured development plans with phased task breakdowns, requirements, and QA checklists. Use when the user explicitly asks to create a dev plan, development plan, or document development requirements.
Use when defining stopping rules for projects, avoiding sunk cost fallacy, setting objective exit criteria, deciding whether to continue/pivot/kill initiatives, or when users mention kill criteria, exit ramps, stopping rules, go/no-go decisions, project termination, sunk costs, or need disciplined decision-making about when to quit.
Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.
Use before committing to a task. Provides complexity analysis and scope assessment. Invoke when user asks "how complex" or before large features.
Start a technical discussion. Discovers research and existing discussions, offers multiple entry paths, and invokes the technical-discussion skill.
Manage Jira issues, sprints, and epics using the jira CLI (ankitpokhrel/jira-cli). Use when asked to create, view, edit, list, move, assign, comment on, link, or delete Jira issues. Also use for sprint operations (list sprints, view current sprint, add issues to sprints) and epic operations (create epics, add/remove issues). Triggers on any Jira-related task, ticket management, sprint planning, or board workflow request.
Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
SCPR (Situation-Complication-Problem-Recommendation) framework for structured problem solving and executive communication. Use when users need to structure strategic arguments, analyze business situations, create executive summaries, or develop clear problem statements using McKinsey-style communication. Apply when structuring recommendations, writing memos, or organizing strategic thinking.
Project management expertise - agile methodology, estimation, risk management, stakeholder management
Manage project state using append-only, time-based Markdown files under /project/. Use when managing multi-epic projects, tracking decisions over time, maintaining audit trails, coordinating distributed teams, or requiring rollback visibility. Forces context loading, explicit confirmation gates, and immutable history preservation.