Total 30,743 skills, Project Management has 1152 skills
Showing 12 of 1152 skills
Create a structured problem statement document for a feature, bugfix, or project. Use when starting a project, adding a feature, or fixing a bug and you need to clearly define the problem, context, desired outcome, and success criteria. Accepts input from Jira tickets (via MCP), document links, or text descriptions.
Evaluate technical options with scoring matrix, trigger Gate 4 for significant decisions
사용자 관점에서 제품 요구사항을 정의할 때 INVEST 원칙을 따르는 포괄적인 유저스토리를 작성합니다.
Event Storming 기법을 사용하여 PlantUML 시퀀스 다이어그램을 작성하고 유저스토리 개발을 준비합니다. 기획 구체화 시 사용하세요.
Portfolio retrospective skill for capturing lessons learned, process improvements, and organizational learning across completed projects.
Issue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue dependencies, relationships, and cloning. NOT FOR: epic linking (use jira-agile), field updates (use jira-issue), bulk cloning (use jira-bulk).
Scaffold a new planning output format adapter. Creates a format directory with all required files implementing the output format contract.
Roadmap Generator - Auto-activating skill for Enterprise Workflows. Triggers on: roadmap generator, roadmap generator Part of the Enterprise Workflows skill category.
Copilot agent that assists with project planning, scheduling, risk management, and progress tracking for software development projects Trigger terms: project management, project plan, WBS, Gantt chart, risk management, sprint planning, milestone tracking, project timeline, resource allocation, stakeholder management Use when: User requests involve project manager tasks.
Implement one prd.json task per iteration using tracer-bullet + compound mindset. Triggers on: ratatouille:.
Ideation: Use for /ideation or when organizing messy brain dumps into structured specs. NOT for existing tickets (use /spec instead).
Plan, update, and audit a high-level project roadmap. Use when asked to "create a roadmap", "plan features", "what should we build next", "update the roadmap", "audit the roadmap", "review project direction", "prioritize features", or when starting a new project and needing to map out future work.