Total 53,554 skills, Project Management has 1940 skills
Showing 12 of 1940 skills
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Business case analysis with ROI, NPV, IRR, payback period, and TCO calculations for investment decisions. Use when building financial justification, cost-benefit analysis, build-vs-buy comparisons, or sensitivity analysis.
GitHub Project health dashboard. Shows workflow distribution, component health, team workload, items needing attention, and available views.
Use when creating durable work items, managing todo lifecycle, or tracking findings across sessions in the file-based todo system
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. Part of the skills-for-java project
Product design, feature planning, and technical architecture for new projects. Explores the problem space through deep requirements gathering, suggests creative features, makes architecture decisions, and produces a structured MVP plan with scope boundaries, a future roadmap, and a deliverable tracker. Uses plan mode for deliberate thinking before writing any artifacts. Use when the user says "mvp", "plan a product", "design features", "what should I build", "feature planning", "scope an MVP", or describes a product they want to plan.
List taxonomy labels in One Horizon (goals, companies, products, releases, components). Use when asked "show taxonomy", "find label IDs", or "tag this initiative". Requires One Horizon MCP.
Use this skill when you need to modify a project (add, delete, or modify files) and want to organically synchronize update_plan with CSV: Create a `{Task Name} TO DO list.csv` file in the project root directory, use TODO/IN_PROGRESS/DONE statuses to drive the pending/in_progress/completed status of the plan, advance tasks synchronously, and delete the file after all tasks are completed.
Project status dashboard — open issues, recent commits, active branches/worktrees, memory state, and scratchpad. Use when the user asks for a status report, project overview, "what's going on", "where are we", or wants to catch up on project state without the full /catchup reconstruction.
Produce a detailed low-level design with API contracts, data models, error handling, test strategy, and dependency version policy. Use after the high-level design is approved.
Use when starting any implementation task, feature request, bug fix, or refactoring work. Triggers on /plan command, before any code is written, when requirements need structured analysis, or when transitioning from brainstorming to implementation. Forces question-asking, approach comparison, and explicit approval before any code.
Manage the lifecycle of ExecPlans — self-contained, living specifications for multi-step work. Creates plans in the correct format, enforces living section updates, and handles the active → completed transition. Use for any work expected to take more than one session or touching more than 3 files. Triggers: "create a plan", "write a plan", "start plan", "continue plan", "resume plan", "finish plan", "complete plan", multi-step features, refactors, or tasks spanning sessions.