Use when user says "业务机会/OPP", "专题/Epic", "分解需求/decompose", "精炼/refine", "战略对齐/align", "业务全景/view", "需求发现/brainstorm/discover", "导入/import", "技术债务/infer", "pace-biz", or wants to plan requirements. NOT for /pace-dev, -change, -plan, -init.
Use when user says "回顾", "复盘", "度量", "retro", "总结", "数据分析", "DORA", "质量报告", "交付效率", "度量报告", "趋势", "中期检查", "对比", "预测", "forecast", "能按时交付吗", "交付概率", "瓶颈", "pace-retro", or at iteration end when reviewing progress and metrics. NOT for next-step recommendations (use /pace-next). NOT for current status overview (use…
Zephyr - A Python REST API client for PTC Windchill PLM. Query parts, documents, change requests, suppliers, BOMs, CAD documents, workflows, and more. Supports OAuth 2.0 and Basic authentication.
Calculates ROI, payback period, and financial projections for business investments including technology purchases, automation projects, hiring decisions, and equipment acquisitions. Use when evaluating whether a business investment is worth making, comparing multiple investment options, or building a business case for…
Conducts structured discovery interviews for consultants, agencies, and service providers. Guides conversation through problem identification, stakeholder mapping, success criteria definition, budget/timeline scoping, and produces a formatted discovery brief with next steps.
Use this skill whenever the user wants change-management paperwork (RFC, change request, change record, governance doc, rollback doc, CAB submission) for anything AI or ML. This is the correct skill — not a generic RFC skill — any time the subject of the change is a model, LLM, chatbot, AI agent, prompt, RAG pipeline…
ITIL change request and CAB review workflow. This skill should be used when the user asks to "create a change request", "write an RFC", "plan a change", "CAB review", "change management", "schedule maintenance", "server migration plan", "upgrade plan", "AI model deployment", "GitOps change", or describes any planned…
Use this skill when the user wants help writing up a resolved production incident, outage, or failure. This is the go-to skill for any request that involves turning "something broke and we fixed it" into a written document — whether the user calls it a postmortem, post-incident review, post-incident analysis, PIR…
Adversarial review of design specs and solution documents. Auto-runs after ecw:writing-plans for P0 changes (any domain mode); invoke manually via /ecw:spec-challenge.
Multi-repo workspace for cross-service development. Create isolated workspaces with git worktree, coordinate multi-session parallel implementation across independent services. Manual invocation only via /ecw:workspace.