Total 50,474 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Comprehensive A3 one-page problem analysis with root cause and action plan
Delivery Report Skill for Team Workflows (Phase 4). Generate PR Description (referencing plans/designs/verification items) and optionally sync with Jira Story.
You must use it before any creative work - creating features, building components, adding functionality, or modifying behavior. Explore user intentions, requirements, and design before implementation.
Identify, assess, and mitigate operational risks. Trigger with "what are the risks", "risk assessment", "risk register", "what could go wrong", or when the user is evaluating risks associated with a project, vendor, process, or decision.
Backlog Management. Users can submit ideas or pain points at any time, and the AI is responsible for following up, organizing, merging, and archiving them into the backlog file. When users are preparing to launch a new version, it assists in filtering from the backlog. Driven by pain points, no advance scheduling is done.
Use when you need to perform D1 research during the Spec-level design phase (output `{FEATURE_DIR}/design/research.md`), or when you face critical uncertainties/high-risk points that require verification first instead of directly proceeding to D2; common symptoms include lack of evidence to support trade-offs, unknown items written as TODOs/to-be-confirmed issues, attempting to guess the FEATURE_DIR under pressure, or writing research as implementation details.
Conduct a systematic analysis of macro-environmental factors—Political, Economic, Social, Technological, Environmental, and Legal—that could impact your product or project. Use this to identify ex
Break down large user stories, epics, or features into smaller, independently deliverable stories using systematic splitting patterns. Use this to make work more manageable, reduce risk, enable faster
Help users break down product requirements into phased version plans. Triggered when users say "split versions", "version planning", "how to build MVP", "phased implementation".
Specification-driven development with structured phases: Initialize, Plan, Tasks, Implement+Validate. Creates structured feature specs with traceability to requirements. Use when: starting projects, planning features, implementing with verification, or tracking decisions across sessions. Also use when the user wants to break a feature into tasks, plan before coding, track implementation progress, set up a new project structure, or organize work into specs and plans. Triggers on "map codebase", "initialize", "initialize project", "create feature", "plan", "tasks", "implement", "validate", "archive", "break this into tasks", "plan this feature", "start a new project".
Use this when you are about to start Discover for an existing project, but you don't know "which portals can be used as evidence (run/test/ci/contract/ops)" and "which modules should be prioritized (P0/P1/P2)", and you are worried that out-of-control scope will lead to unmaintainable results.
Эксперт по статус-отчётам. Используй для создания шаблонов отчётов, executive summaries и project dashboards.