Classify Task Complexity

Analyze a task description to determine whether it should use the lightweight tinyspec workflow or the full SDD workflow (specify → plan → tasks → implement). Acts as an intelligent router that saves time on small tasks and ensures proper process for complex ones.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty). The user describes what they want to build or fix.

Prerequisites

1. Verify a spec-kit project exists by checking for .specify/ directory
2. Verify the user has described the task (if not, ask what they want to build)

Outline

1. Analyze the task: Evaluate the task description against complexity signals:

Small task signals (→ tinyspec):

Large task signals (→ full SDD):

1. Estimate scope: Quick estimation based on available information:

• Files affected: How many files will likely change
• Task count: How many distinct implementation steps
• Risk level: How likely is this to break existing functionality
• Dependencies: Does this require coordination across modules

1. Classify and recommend:

1. Output recommendation:

   # Task Classification

   | Factor | Assessment |
   |--------|-----------|
   | **Task** | {task description} |
   | **Complexity** | 🟢 Small / 🟡 Medium / 🔴 Large |
   | **Estimated files** | ~{N} files |
   | **Estimated tasks** | ~{N} tasks |
   | **Risk** | Low / Medium / High |

   ## Recommendation

   → Use **`/speckit.tinyspec`** — this is a small, well-scoped change.

   OR

   → Use **`/speckit.specify`** — this task has enough complexity to benefit from the full SDD workflow.

Rules

• Read-only — this command never modifies any files
• Default to tinyspec — when in doubt between small and medium, recommend tinyspec (users can always upgrade)
• Explain the reasoning — always tell the user why you classified the task as small/medium/large
• No blocking — this is a recommendation, not a gate. Users can choose either workflow regardless
• Context-aware — consider the project's codebase size and architecture when estimating scope