analyzing-specifications

Use when analyzing requirements or project specifications - guides shannon analyze command, explains 8D complexity output, caching behavior, context-aware mode with --project flag

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The Analyzing Specifications skill leverages the Shannon Framework to perform deep 8D complexity analysis on project requirements. It provides quantitative insights, including complexity scores, resource requirements (time and agent count), and domain-specific distributions, enabling precise technical planning and automated phase mapping for software development lifecycles.

Use Cases

  • Requirement Scoping: Automatically evaluate the complexity of new project specifications to determine if they are simple, moderate, or critical, helping teams allocate the right number of developers and set realistic deadlines.
  • Context-Aware Planning: Use the --project flag to analyze new feature requests against an existing codebase, identifying specific module impacts and maintaining architectural consistency by referencing existing tech stacks.
  • Resource & Timeline Estimation: Generate structured 5-phase execution plans with estimated timelines and task breakdowns to streamline the transition from raw specifications to actionable development roadmaps.
  • Automated Workflow Integration: Utilize the --json output to pipe complexity data into internal project management dashboards or CI/CD pipelines for automated reporting and cost-efficient analysis via built-in caching.
nameanalyzing-specifications
descriptionUse when analyzing requirements or project specifications - guides shannon analyze command, explains 8D complexity output, caching behavior, context-aware mode with --project flag

Analyzing Specifications

Overview

shannon analyze invokes Shannon Framework spec-analysis skill to perform 8D complexity analysis with automatic caching.

Basic Usage

shannon analyze project_spec.md
shannon analyze spec.md --json > analysis.json
shannon analyze spec.md --project myapp  # Context-aware

Output Interpretation

8D Complexity Score (0.00-1.00):

  • 0.00-0.30: Simple (hours-1 day, 1-2 agents)
  • 0.30-0.50: Moderate (1-2 days, 2-3 agents)
  • 0.50-0.70: Complex (2-4 days, 3-7 agents)
  • 0.70-0.85: High (1-2 weeks, 8-15 agents)
  • 0.85-1.00: Critical (2+ weeks, 15-25 agents)

Domain Distribution: Frontend, Backend, Database, Mobile, DevOps percentages

Phase Plan: 5 phases with timelines and tasks

Caching

Automatic:

  • First run: API call (~$0.02, 30-60s)
  • Second run: Cache hit (<500ms, $0.00)
  • TTL: 7 days
  • Check: shannon cache stats

Context-Aware Mode

For existing projects:

# 1. Onboard project first
shannon onboard /path/to/project --project-id myapp

# 2. Analyze with context
shannon analyze new_feature.md --project myapp

With context: Mentions existing modules, patterns, tech stack. Without context: Generic recommendations.

Options

  • --json: JSON output for automation
  • --project ID: Context-aware analysis
  • --no-cache: Skip cache (force fresh analysis)
  • --session-id ID: Custom session tracking