安全扫描
OpenClaw
安全
high confidenceThe skill is an instruction-only project scenario-planning helper whose requirements and runtime instructions match its stated purpose and do not request extra privileges or external installs.
评估建议
This skill is coherent and low-risk: it provides step-by-step guidance for scenario analysis and doesn't request credentials or install code. Before using it, ensure you supply a proper baseline project file (and keep backups), confirm any file edits are done on a duplicated baseline (the SKILL.md already recommends this), and review outputs before applying changes to live plans. If you expect probabilistic (Monte Carlo) analysis rather than deterministic scenarios, ask for that explicitly. If y...详细分析 ▾
✓ 用途与能力
Name and description (what-if scenario planning for schedules/costs/resources) align with the SKILL.md content. There are no unrelated environment variables, binaries, or config paths requested.
✓ 指令范围
Runtime instructions stay within project-scheduling scope (baseline, variables, modify model in Excel/MS Project/Primavera, simulate and compare). Instructions do not ask to read unrelated system files, call external endpoints, or access secrets.
✓ 安装机制
No install spec or code files are present (instruction-only). This minimizes disk writes and external code execution risk.
✓ 凭证需求
The skill requests no environment variables, credentials, or config paths. Required access is limited to the user's project data (Excel/MS Project/Primavera files) implied by the purpose.
✓ 持久化与权限
always is false and default model invocation is allowed (normal). The skill does not request permanent presence or system-wide configuration changes.
安全有层次,运行前请审查代码。
运行时依赖
无特殊依赖
版本
latestv1.0.22026/3/31
**Summary:** Major refocus toward concise, practical what-if scenario planning for project management. Support files and much theory removed. - Streamlined the skill to focus on deterministic what-if scenario analysis (WISA) for projects. - Removed extensive methodology descriptions and all external reference files. - Clearly structured step-by-step process for simulating project plan changes in schedule, resources, or costs. - Added specific guidance for using Excel, MS Project, and Primavera tools. - Provides a simple, consistent output and evaluation format for scenario impacts and recommendations. - Enforces baseline validation and limits complexity for practical real-world use.
● 无害
安装命令
点击复制官方npx clawhub@latest install scenario-planning
镜像加速npx clawhub@latest install scenario-planning --registry https://cn.longxiaskill.com
技能文档
# What-if Scenario Planning (WISA)
When to Use
Use this skill when:- A project plan needs risk simulation before execution
- The user asks “what if this changes?” in a project context
- There is uncertainty in schedule, cost, or resources
- The user is working in Excel, MS Project, or similar tools
Core Objective
Simulate alternate project scenarios by modifying key variables (duration, resources, cost) and evaluate their impact on:- Project timeline
- Critical path
- Total cost
- Resource utilization
Execution Steps
Step 1: Establish Baseline Plan
Ensure a complete baseline exists:- Tasks with durations
- Dependencies (network/PERT)
- Resources assigned
- Cost estimates
Step 2: Identify Variables
Extract or ask for uncertain variables:- Resource availability
- Task duration variability
- Budget constraints
- External risks (delays, logistics, approvals)
Step 3: Define Scenario
Create a structured scenario: Format:- Scenario Name:
- Variable Change:
- Duration/Impact Change:
- Time Window (if applicable):
- Resource A unavailable for 3 days starting Day 10
Step 4: Modify Project Model
If Excel:- Adjust input cells (duration/resource %)
- Use:
- Duplicate baseline
- Modify:
Step 5: Simulate Impact
Recalculate project plan and capture:- New project duration
- Critical path changes
- Cost variation
- Delayed milestones
Step 6: Compare with Baseline
Create structured comparison: | Metric | Baseline | Scenario | |--------|----------|----------| | Duration | | | | Cost | | | | Critical Path | | |Step 7: Evaluate Acceptability
Decide:- Acceptable → proceed with scenario plan
- Not acceptable → propose mitigation:
Step 8: Recommend Action
Always provide:- Impact summary
- Decision recommendation
- Optional mitigation strategies
Output Format
Return results in this structure:Scenario Summary
- Scenario:
- Key Change:
Impact Analysis
- Duration Change:
- Cost Impact:
- Critical Path Impact:
Recommendation
- Decision:
- Suggested Actions:
Rules
- Do NOT simulate without a baseline
- Limit scenarios to avoid combinatorial explosion
- Prefer clarity over complexity
- Always quantify impact (time/cost)
- If data is missing → ask user before proceeding
Notes
- This is deterministic scenario analysis (WISA)
- For probabilistic analysis, suggest Monte Carlo simulation
- Best used during planning and scheduling phase
Validation
Before finalizing:- Ensure dependencies are preserved
- Check calculations consistency
- Validate assumptions with user context
- Confirm outputs are realistic (no negative durations, etc.)