pm-evaluate-complexity

Categorize project complexity from analysisContext estimates and taskType into JSON output.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/munlucky/claude-command-relay --skill pm-evaluate-complexity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-evaluate-complexity
Source: https://github.com/munlucky/claude-command-relay/tree/main/.claude/skills/pm-evaluate-complexity
Command: npx skills add https://github.com/munlucky/claude-command-relay --skill pm-evaluate-complexity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes analysis context data (estimatedFiles, estimatedLines, estimatedTime, and taskType) to assign a clear complexity level (simple, medium, complex) and prepares a structured patch output for downstream processing.

Core Features & Use Cases

  • Evaluate complexity by inspecting analysisContext.estimates and analysisContext.request.taskType.
  • Produce a patch-like JSON containing complexity, estimates, and optional notes for traceability.
  • Use in planning, scoping, and resource estimation to improve sprint forecasting and workload allocation.

Quick Start

Provide a patch JSON that reflects the computed complexity and estimates based on the given analysis context.

Frequently Asked Questions about pm-evaluate-complexity

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

FAQPage Schema
How do I evaluate project complexity from time and file estimates?

Project complexity is evaluated by analyzing estimatedFiles, estimatedLines, and estimatedTime data to categorize the workload as simple, medium, or complex, returning a structured JSON output for downstream planning and resource allocation.

How do I categorize task workload for sprint forecasting?

You categorize task workload by inspecting analysisContext estimates and taskType, assigning a clear complexity level of simple, medium, or complex, and producing a patch-like JSON with workload details and optional notes for traceability.

What data do I need to determine project complexity levels?

Determining project complexity levels requires providing analysis context data including estimatedFiles, estimatedLines, estimatedTime, and taskType, which are processed to generate a structured complexity patch output.

Can I use estimated lines and files to generate a JSON patch for scoping?

Yes, estimated lines and files can generate a JSON patch for scoping, as the Skill computes a patch-like JSON structure containing the complexity level, original estimates, and notes for downstream processing.

Does task type affect how project complexity is calculated?

Task type does affect project complexity calculation, as the Skill evaluates complexity specifically by inspecting analysisContext.estimates alongside analysisContext.request.taskType to assign the final simple, medium, or complex categorization.