Total 55,016 skills, Project Management has 2008 skills
Showing 12 of 2008 skills
Create session retrospective with AI diary and lessons learned. Use when user says "rrr", "retrospective", "wrap up session", "session summary", or at end of work session.
Convert ambiguous user requests into structured USDM requirements documents. Decomposes requirements into Requirement → Reason → Description → Specification hierarchy. Integrates with GitHub Issues, Asana, and Jira tickets as input sources. Use when: "create requirements", "write requirements document", "USDM", "decompose requirements", "requirements definition", "要件定義", "要件を整理", "要件分解".
Resume work from handoff document with context analysis and validation
Creates and manages project artifacts (research, spikes, analysis, plans) using templated scripts. Use when asked to "create an ADR", "research topic", "spike investigation", "implementation plan", or "create analysis". Provides standardized structure, naming conventions, and helper scripts for artifact organization. Works with .claude/artifacts/ directory, Python scripts, and markdown templates.
Plan and optimize resource allocation. Trigger with "resource planning", "capacity", "utilization", "staffing plan", "who should work on what", "we're stretched thin", or when the user needs help allocating people, budget, or time across projects and teams.
Analyze and improve business processes. Trigger with "this process is slow", "how can we improve", "streamline this workflow", "too many steps", "bottleneck", or when the user describes an inefficient process they want to fix.
Use when reviewing a plan before implementation begins. Not for autonomous plan analysis — use plan-review agent instead. Challenges scope, walks through architecture/quality/tests/performance interactively with mandatory user checkpoints and opinionated recommendations.
Execute an approved implementation plan exactly and safely. Use when a plan already exists (for example in docs/plans/...) and work must be carried out phase-by-phase with verification checkpoints, status tracking, and final execution reporting.
Generate and maintain changelogs following Keep a Changelog and Conventional Commits standards. Use when releasing versions, documenting changes, or updating project history.
Build a World Code business strategy. This is the hub skill that tracks progress across all seven World Code elements and routes to the next one. Use when someone says "build my world code", "start my business strategy", "world code", "world code start", "business strategy framework", or asks about building a business around their worldview.
End-to-end workflow for taking a new tool idea from research to working MVP. Use when the user has an idea for a CLI tool, library, or small project and wants to go from concept to initial implementation. Triggers on "I have an idea for a tool", "build a new CLI", "create a new project", "kickoff new tool", "I want to build", "let's build a new", "新しいツールを作りたい", "CLIを作る".
Interact with the Overvy kanban board via curl. Use when the user wants to list issues, list AI tickets, work on a ticket, move issues between lanes, or check board status. Triggers include "overvy", "list AI tickets", "show me ready tickets", "what tickets are available", "what should I work on", "work on ticket", "work on any ticket", "pick a ticket", "start a ticket", "pick up an issue", "my issues", "kanban board", "move issue", "list issues", "board status", or references to lanes like "ready", "in progress", "in review", "done". Requires OVERVY_API_KEY environment variable.