agentcmd: Command for Claude Code

Estimate Spec Complexity

Analyze an existing spec file and add/update complexity estimates for all tasks and phases.

Variables

• $specIdentifier: $1 (required) - One of:
  • Spec ID (e.g., ef3)
  • Full path (e.g., .agent/specs/todo/ef3-auth-improvements-spec.md)
  • Feature name (e.g., auth-improvements)

Instructions

• IMPORTANT: Use your reasoning model - THINK HARD about task complexity based on context needs
• Locate the spec file from the provided identifier
• Read and parse the existing spec (supports markdown and json formats)
• Analyze each task and assign complexity score (1-10) based on context requirements
• Calculate phase totals and average complexity
• Update the spec file with complexity data while preserving all existing content
• Can be run multiple times to re-estimate if complexity scores already exist
• DO NOT include hour-based estimates - use complexity points only

Complexity Scale (Context-Focused)

Assign complexity based on context window usage and cognitive load, not time:

• 1-2/10: Trivial - Single file, <50 lines changed, minimal context (config, doc, simple type)
• 3-4/10: Simple - Few files, straightforward logic, low context (single endpoint, basic component)
• 5-6/10: Moderate - Multiple related files, moderate context (DB field + migration + API update)
• 7-8/10: Complex - Cross-cutting change, high context, multiple domains (full-stack feature, state refactor)
• 9-10/10: Very complex - Architectural change, deep codebase knowledge required (major refactor, complex integration)

Key principle: Higher complexity = more context the agent needs to load and understand

Workflow

1. Locate Spec File:
   • If $specIdentifier is a full path (contains /):
     • Use that path directly
   • Otherwise, look up in .agent/specs/index.json:
     • For numeric ID: Match by id field
     • For feature name: Fuzzy match folder name (e.g., message-queue matches ef3-message-queue-implementation/spec.md)
     • Use path from index: .agent/specs/{path}
   • If not found in index.json, fallback to directory search:
     • Search in order: .agent/specs/backlog/, .agent/specs/todo/, .agent/specs/done/
     • For ID: Pattern {id}-*/spec.{md,json}
     • For feature name: Pattern *{feature-name}*/spec.{md,json} (fuzzy match)
   • If still not found, report error