Total 54,172 skills, Project Management has 1983 skills
Showing 12 of 1983 skills
Use when order-of-magnitude cost estimates are needed to assess financial feasibility, compare cost-effectiveness of alternatives, or identify major cost drivers (not for detailed quotes—that's Procurement)
Changelog generation, release notes, and semantic versioning. Use when user asks to "write a changelog", "generate release notes", "bump version", "follow conventional commits", "create a release", "update CHANGELOG.md", or any versioning and release documentation tasks.
Create implementation plan documents with development phases, sequencing, and actionable tasks. Works through 3 phases (structure, approach, generation) following established feature development process. Use when creating plan.md documents from technical specs. Triggers on "create implementation plan", "plan this feature", "sequence the development".
Drafts initial ticket requirements by asking targeted clarifying questions and producing a structured ticket with Title, Body, and Acceptance Criteria. Use when a user has a request that needs to be converted into a clear tracker-ready ticket without codebase or architecture analysis.
Create a living specification (Spec) or plan for a feature by analyzing requirements and codebase
Execute approved implementation plans from scratchpad. Use when implementing a previously planned feature.
Review daily Jira worklogs, calculate logged time vs 8h target, suggest existing issues, or create new TL issues and log work when needed.
Use this when the Discover (reverse engineering) of legacy projects tends to get out of control in coverage. You need to first conduct module classification (P0/P1/P2) and constrain the depth of reverse engineering, ensuring that high-ROI modules are made traceable first instead of "writing everything but making it unmaintainable."
Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses Socratic questioning to capture intent before drafting, and validates output against an agent-readiness checklist.
Breaking changes documentation, migration guides, deprecation process, and versioning. Use when introducing breaking API changes, creating migration guides, deprecating features, updating changelogs, managing major version releases, or documenting version transitions. Triggered by keywords like breaking changes, migration guide, deprecation notice, version upgrade, changelog update, breaking API modification.
Create and maintain a repository-root ROADMAP.md as the single source of truth for project milestones and accepted plans. Use when bootstrapping any new project, accepting/completing a plan, defining or updating milestone/version roadmaps, marking milestones as reached/changed/de-scoped, or answering where roadmap and milestone status should be referenced.
Creates a comprehensive action plan that addresses both substance (strengthening your proposal, filling evidence gaps, doing research) and politics (winning over key people, sequencing conversations, handling objections). Use after /clarify or when you need to turn a goal into concrete actions that make your case stronger AND navigate the people involved.