Total 53,693 skills, Project Management has 1949 skills
Showing 12 of 1949 skills
Plans PM career growth using frameworks from 40+ career episodes and Ami Vora's advancement strategies. Use when planning promotions, identifying skill gaps, navigating career transitions, or choosing between IC and management paths.
Beans-driven Ralp loop for beans-enabled repos. Use either to work on one bean on user request or to work on all beans in a repo.
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.
Headcount planning, org design, and team structure optimization. Trigger with "org planning", "headcount plan", "team structure", "reorg", "who should we hire next", or when the user is thinking about team size, reporting structure, or organizational design.
操作 CNB (cnb.cool) 平台上的 Issue。当用户需要创建、查询、更新 CNB 上的 Issue， 或需要管理 Issue 的标签、处理人、评论时，使用此 skill。 触发词: cnb issue、cnb 问题单、腾讯代码平台 issue、cnb.cool issue、cnb工单
Use when working on the spec branch of sdlc-dev, when requirements are ambiguous, scope is unstable, constraints are unclear, and issues such as context drift, unfounded assumptions, multiple questions asked at once, or requests to skip the FEATURE_DIR/raw gate occur.
Use when you need to perform D1 research during the Spec-level design phase (output `{FEATURE_DIR}/design/research.md`), or when you face critical uncertainties/high-risk points that require verification first instead of directly proceeding to D2; common symptoms include lack of evidence to support trade-offs, unknown items written as TODOs/to-be-confirmed issues, attempting to guess the FEATURE_DIR under pressure, or writing research as implementation details.
Conduct a systematic analysis of macro-environmental factors—Political, Economic, Social, Technological, Environmental, and Legal—that could impact your product or project. Use this to identify ex
In-repo planning and specification system for software projects. Use when asked to "create a plan", "write a spec", "document a proposal", "blueprint a feature", or when doing architectural planning work.
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
Update a TODO task in One Horizon. Use when asked to "mark this todo done", "update this task", or "edit this TODO". Do not use for initiatives or bug/feature-request updates. Requires One Horizon MCP.