Total 50,474 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Challenges stakeholder requests to identify real needs and propose optimal solutions. Use when receiving vague feature requests, reframing a problem before implementation, or when user mentions problem framing, XY problem, stakeholder request, or solution discovery. WHEN NOT: Well-defined technical tasks with clear requirements, bug fixes with known root causes, or routine CRUD operations.
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
Retrieve ALL information from a Jira ticket (description, comments, subtasks, attachments metadata, labels, sprint, status, assignee, reporter, linked issues, custom fields, acceptance criteria) and persist it as a single Markdown file. Use whenever the user says "fetch ticket", "retrieve Jira", "pull ticket info", "get ticket details", "look up ticket", "grab the Jira", "what does ticket X say", "check the ticket", "read the ticket", "show me the ticket", or provides a Jira ticket URL or key like PROJECT-1234. Also triggered by the orchestrating-jira-workflow skill as Phase 1 of the end-to-end pipeline. Trigger even if the user only pastes a ticket key with no other context — that alone means "fetch this ticket." This skill ONLY retrieves — it never modifies the ticket or starts implementation.
Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.
Use before any non-instant feature work, refactor, behavior change, or requirements-shaping conversation where user intent is not yet locked. Extracts and confirms the decisions that planning will depend on, especially when the user knows what they want but has not fully thought through edge cases, scope boundaries, or expected behavior. Output is CONTEXT.md.
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth for execution checklist and status, SSOT), and provide an unambiguous task list for subsequent I2 execution.
Use when breaking work into discrete steps, tracking progress through multi-step implementations, or managing implementation task lists. Triggers when an approved plan needs to be converted into tracked tasks, when progress reporting is needed during execution, or when checkpoint reviews are required between task batches.
Produce a high-level technical design with architecture diagram, component responsibilities, data flow, and test scenario map. Use after the product intent specification is approved.
Reconcile roadmap milestone state against active and archived changes.
Nozbe Teams integration. Manage Users, Organizations. Use when the user wants to interact with Nozbe Teams data.
Breeze integration. Manage data, records, and automate workflows. Use when the user wants to interact with Breeze data.