effort_and_risk

Generate structured effort estimates and risk assessments from plan_complete issues.

1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/SorraTheOrc/SorraAgents --skill effort-and-risk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effort_and_risk
Source: https://github.com/SorraTheOrc/SorraAgents/tree/main/skill/effort_and_risk
Command: npx skills add https://github.com/SorraTheOrc/SorraAgents --skill effort-and-risk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires wl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The Skill automates the production of auditable engineering estimates for a prepared work item, including both effort and risk, to improve planning transparency and traceability.

Core Features & Use Cases

  • WBS-based estimation: derives a lightweight Work Breakdown Structure from the issue's children to anchor scope.
  • Three-point estimation (PERT): computes expected effort from Optimistic, Most Likely, and Pessimistic values and exposes a final recommended value.
  • Risk scoring: aggregates parent/child risk into a level (Low/Medium/High/Critical) with top drivers and mitigations.
  • Outputs: produces a machine-readable JSON object and a human-readable summary for posting in issue comments.

Quick Start

Trigger the skill with a plan_complete issue and run the orchestrator to produce the final JSON estimate.

Frequently Asked Questions about effort_and_risk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate auditable engineering effort estimates from a work breakdown structure?

To generate auditable engineering effort estimates, ingest a fully planned issue to automatically derive a work breakdown structure from child items and compute expected effort, overheads, and risk.

How does PERT three-point estimation calculate expected effort?

PERT three-point estimation calculates expected effort by evaluating Optimistic, Most Likely, and Pessimistic hour values from the work breakdown structure to expose a final recommended effort estimate.

How do I assess and aggregate project risk levels for engineering planning?

Project risk assessment aggregates parent and child risk factors into a Low, Medium, High, or Critical risk level, outputting top risk drivers and recommended mitigations alongside the effort estimate.

What format are effort estimation results output in for issue tracking?

Effort estimation results are output as a machine-readable JSON payload containing effort, risk, confidence, assumptions, and unknowns, plus a human-readable summary for posting in issue comments.

Do I need a completed issue plan before running effort and risk estimation?

Yes, effort and risk estimation requires a plan_complete issue with a detailed plan and child items to derive the work breakdown structure needed for computing O/M/P hours and risk scores.

What is the best way to improve planning transparency for engineering tasks?

The best way to improve planning transparency is to automate the production of auditable estimates, providing traceable effort calculations, risk levels, and documented assumptions directly in issue comments.