speckit-tinyspec-classifylisted

# 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 ```text $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): | Signal | Example | |--------|---------| | Single UI component change | "Add a logout button" | | Bug fix with known location | "Fix date format in invoices" | | Config or environment change | "Add new env variable for API key" | | Simple validation addition | "Add email validation to signup" | | Copy/text update | "Update error messages" | | Single endpoint addition | "Add GET /health endpoint" | | Styling change | "Make the sidebar responsive" | **Large task signals** (→ full SDD): | Signal | Example | |--------|---------| | Multiple modules affected | "Add user authentication system" | | New database tables/schema | "Add a comments feature with threading" | | Architectural cha