Total 50,320 skills, Project Management has 1841 skills
Showing 12 of 1841 skills
/cs:execute <decision> — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.
季度 banner + 3 个目标 + KR 进度条 + owner + 状态 pill
标题 + 出席 + 议程 + 决议 + action items + 下次
Produces calibrated three-point PERT estimates (best/likely/worst) with confidence intervals, unknowns, and assumptions. Triggers on: "estimate this", "how long will this take", "effort estimate", "confidence interval", "story points", "t-shirt sizing". NOT for task decomposition, use task-decomposer.
Summarises the current working session — what was worked on, what was achieved, what remains, and any blockers. Use at the end of a session or when handing off work.
Conducts retrospective with learnings and improvement actions. Use when a cycle, sprint, or delivery has ended and the team needs to reflect on what worked and what needs to change. Also absorbs post-implementation reflection aspects.
Routes to the appropriate agile skill based on context. Use when you need guidance on which skill to use — whether for planning, ceremonies, or tracking.
Render the current plan as a high-DPI PNG dependency DAG — nodes are issues / sub-issues / PRs, edges come from sub-issue links plus dependency-language prose ("Depends on", "Part of", "Blocks", "Closes") and PR / commit cross-references, and every node is color-coded done / in-progress / available-next / blocked so sequencing and critical path are obvious at a glance. Use when asked "plan as dag", "draw a dag", "dag diagram", "show the dependency graph", "what's blocking what", "what's the critical path", "what can be parallelized", "what's left for
Run a structured business analysis workflow: requirements elicitation with stakeholder interviews and MoSCoW prioritization, as-is/to-be process mapping with BPMN notation, data-driven analysis (CBA, SWOT, root cause), and production-ready documentation (BRD, FRD, user stories with INVEST acceptance criteria). Triggers on "gather requirements", "write user stories", "map business process", "BRD", "FRD", "gap analysis", "cost-benefit analysis", "facilitate workshop", "business requirements", "process mapping", "as-is to-be", "stakeholder interview", or "business analyst". For management consulting (issue trees, steerCo business cases, operating model), use business-consultant—not business-analyst. For business model canvas, market sizing, and unit economics research, use business-model-researcher. Human data / labeling platform PRDs: product-management-human-data-platform. Monetization PRDs and packaging: product-management-monetization.
This skill should be used when the user asks about enterprise strategy, corporate strategy, business unit strategy, portfolio prioritization, strategic roadmap, growth strategy, diversification, operating model, capability map, strategic initiative, enterprise transformation, board strategy, scenario planning, or competitive positioning at enterprise level. Guides corporate and BU strategy, portfolio prioritization, growth and diversification, market positioning, operating model and capabilities, transformation roadmaps, M&A/partnership/divestiture framing (strategy—not legal DD), scenarios, executive alignment, and KPI trees—not product backlog or program RAID (technical-program-manager), financial models only (financial-analyst), contracts (commercial-counsel), cloud or system architecture alone (enterprise-cloud-architect, senior-system-architecture), or consulting workshops without enterprise portfolio scope (business-consultant).
Guides senior corporate transaction leadership—deal thesis, valuation and offer strategy, negotiation priorities, structure (cash/stock/earnout/RWI/locked box), IC and board recommendations, adviser and banker management, go/no-go and walk-away, and oversight of execution through close. Use when leading an M&A, divestiture, financing, or JV as deal principal, preparing investment committee or board materials, setting negotiation mandates, or adjudicating price/structure—not for closing matrices and diligence logistics (transaction-manager), contract drafting (corporate-counsel, commercial-counsel), general strategy consulting (business-consultant), or sales quote-to-cash (deal-operations-administrator). Human executives and counsel approve binding terms.
Reframes messages, requirements, metrics, and decisions for organizational audiences—engineering, product, finance, legal, compliance, sales, operations, actuarial, and executive—by detecting jargon, surfacing implicit assumptions, producing dual-audience briefs, RACI-aligned handoffs, owner-tagged meeting actions, technical-to-business and business-to-technical translation, and escalation summaries. Use when translating for engineering, explaining to finance, cross-department bridging, rewriting for executives, business-friendly versions, technical summaries for leadership, inter-team handoffs, department jargon, or dual-audience briefs—not external customer or brand copy (communication-lead), contract redlines (commercial-counsel), full multi-team program execution (technical-program-manager), human-language i18n/l10n product strings, or strategy-only consulting without audience reframing (business-consultant).