Total 53,944 skills, Project Management has 1958 skills
Showing 12 of 1958 skills
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.
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
Transform specifications into implementation plans with architecture design and dependency-ordered tasks. Use for spec-to-plan conversion, task breakdown, effort estimation. Skip if no spec exists.
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.
Use when every architecture and implementation decision must be traceable with explicit rationale; pair with architect-stack-selector and addon-human-pr-review-gate.
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を作る".
Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now/Next/Later view from scratch.