Total 50,472 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Update the workflow status of tasks
Orchestrate the full one-person company workflow across all OPC skills. It is used when Codex needs to start, continue, or review the complete One Person Company (OPC) methodology process, read prior outputs from `opc-doc/`, determine the user's familiarity with relevant concepts and preferred interaction mode, explain terms when needed, ask one question at a time, offer user-selectable options, and summarize the next concrete action for Chinese-speaking users.
Archive accumulated phase directories from completed milestones
Start a new milestone cycle update PROJECT.md and route to requirements
Use historical analogies to inform strategic decisions by identifying structural similarities and differences between past and present situations. Use this skill when the user draws on historical precedent to justify a strategy, needs to evaluate whether a historical comparison is valid, or wants to learn from past events — even if they say 'this is like the dotcom bubble', 'history repeats itself', or 'what can we learn from how X handled this'.
Apply real options analysis to value managerial flexibility embedded in investment decisions. Use this skill when the user needs to evaluate projects with significant uncertainty and flexibility, assess the value of deferring or expanding investments, compare traditional NPV with expanded NPV, or when they ask 'should we wait to invest', 'what is the option to abandon worth', or 'why does NPV undervalue this project'.
Design and implement OKR (Objectives and Key Results) for goal-setting and strategic alignment across organizational levels. Use this skill when the user needs to set team or company goals, align departments to strategy, track quarterly progress, or transition from KPI to OKR systems — even if they say 'set our quarterly goals', 'how does OKR work', 'align team goals with company vision', or 'our goals feel disconnected'.
Use when new insights change the scope, acceptance criteria, domain language, or technical constraints of an existing Epic, Feature, or Task — for example "refine epic
Breaks down the design into an atomic, ordered, and verifiable task plan stored in tasks.md. Trigger: /sdd-tasks <change-name>, task plan, break down implementation, task breakdown.
Manages a GitHub Project board + Issues as the source of truth for product backlog, tasks, stories, and bugs. Provides three flows: bootstrap (/track-init), track (/track), and query (/backlog). Uses gh CLI for project operations and MCP tools for issue creation. Trigger: /track-init, /track <description>, /backlog, "qué tenemos pendiente?", "what's pending?", "acordate que hay que...", "remember to...", or when SDD generates tasks via sdd-tasks.
Closes a completed SDD change by saving an archive report to engram and optionally updating ai-context/ memory. Trigger: /sdd-archive <change-name>, archive change, finalize SDD cycle, close change.