complexity-assessment

Evaluate task requirements to classify complexity and guide planning phases.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/meetpradeepp/agentic_migration --skill complexity-assessment-meetpradeepp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: complexity-assessment
Source: https://github.com/meetpradeepp/agentic_migration/tree/main/.github/skills/complexity-assessment
Command: npx skills add https://github.com/meetpradeepp/agentic_migration --skill complexity-assessment-meetpradeepp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Complexity Assessment skill provides a structured approach to evaluating task requirements and assigning accurate complexity levels to guide downstream planning and routing.

Core Features & Use Cases

  • Complexity tiering: classify tasks into SIMPLE, STANDARD, or COMPLEX to match appropriate workflows.
  • Multi-dimension analysis: assess scope, integrations, infrastructure, knowledge, and risk to produce a holistic risk profile.
  • Decision-ready outputs: generate standardized metadata (including recommended phases) for use by planning and validation agents.
  • Use Case: route a feature request to quick_spec or a full research-led specification based on assessed complexity.

Quick Start

  1. Provide a requirements.json describing the task (including task_description and workflow_type) and place it in the task input.
  2. Run the complexity assessment to generate complexity_assessment.json.
  3. Review the metadata to guide subsequent planning and validation steps.

Frequently Asked Questions about complexity-assessment

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

FAQPage Schema
How do I evaluate task complexity for software requirements gathering and planning?

To evaluate task complexity for requirements gathering, analyze task requirements to determine true complexity across scope, integrations, infrastructure, knowledge, and risk. This produces a structured complexity assessment that guides downstream planning and routing decisions.

What is the best way to classify project tasks into simple, standard, or complex tiers?

Classifying project tasks into simple, standard, or complex tiers requires a multi-dimension analysis of scope, integrations, infrastructure, knowledge, and risk. This holistic risk profile matches tasks to appropriate workflows and generates decision-ready metadata.

How do I route a feature request to quick_spec or full research-led specification?

Route a feature request to quick_spec or a full research-led specification by running a complexity assessment on the task requirements. The resulting metadata determines whether the workload is simple enough for quick_spec or requires full research validation phases.

Can I analyze workflow risk and complexity using a structured requirements.json input?

Yes, you can analyze workflow risk and complexity by providing a requirements.json file containing task_description and workflow_type. Running the assessment generates a complexity_assessment.json detailing scope, integrations, infrastructure, knowledge, and risk.

What downstream planning phases are recommended after assessing task complexity?

After assessing task complexity, the recommended downstream planning phases include routing to quick_spec, requirements, research, and validation phases. The structured assessment outputs standardized metadata to guide these subsequent planning and validation agents.

Does complexity tiering work for simple to complex workloads across different planning scenarios?

Complexity tiering works across simple to complex workloads by evaluating task requirements to determine true complexity. It is applied to requirements gathering and planning, generating decision-ready metadata for use by planning and validation agents regardless of workload size.