complexity-assessment

Score software tasks across seven dimensions to output a complexity tier.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to gauge the true complexity of a task, leading to mismatches between planning depth and execution effort.

Core Features & Use Cases

  • 7-dimension scoring (scope, integration, infrastructure, knowledge, risk, testing, decomposability) to determine a project tier (SIMPLE, STANDARD, COMPLEX).
  • Contextd integration for memory-based reasoning and rationale when available; inline fallback if contextd is not present.
  • Guided workflow for brainstorming and scoping, including optional decomposition suggestions and integration hints for GitHub planning and branch budgeting.
  • Use Case: Before starting a feature, run complexity assessment to decide whether a simple issue or an epic with sub-issues is warranted.

Quick Start

Run the complexity assessment during /brainstorm Phase 2 with your feature description, then proceed with tier-based planning.

Frequently Asked Questions about complexity-assessment

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

FAQPage Schema
What is task complexity assessment and how does it optimize software project planning?

Task complexity assessment scores seven dimensions like scope, integration, and risk to determine a project tier, optimizing planning by matching execution effort to the appropriate planning depth.

How do I estimate feature complexity before starting development to decide between a simple issue or an epic?

You can estimate feature complexity by running a structured assessment during brainstorming and scoping phases, which outputs a tier classification with confidence to guide worktree needs and artifact granularity.

What dimensions should I evaluate when analyzing risk and complexity for software feature sizing?

Evaluating risk and complexity for feature sizing requires scoring seven dimensions: scope, integration, infrastructure, knowledge, risk, testing, and decomposability to determine the overall project tier.

Can I use this complexity assessment skill without contextd installed?

Yes, you can use the complexity assessment without contextd by relying on the inline fallback mechanism, which provides standard scoring when the memory-based reasoning integration is not present in your environment.

When should I run a complexity assessment during the brainstorming and scoping workflow?

Run complexity assessment during the second phase of brainstorming with your feature description, using the resulting tier classification to proceed with tier-based planning and branch budgeting decisions.

Does complexity assessment provide integration hints for GitHub planning and branch budgeting?

Yes, the guided workflow includes optional decomposition suggestions and integration hints for GitHub planning and branch budgeting based on the tier output and seven-dimension scoring results.