speckit-tinyspec-classify

Name: speckit-tinyspec-classify
Availability: InStock
Author: OpsMill

Classify task descriptions to recommend tinyspec or full SDD workflow.

9|4|Updated May 13, 2025

Search Tags:#sdd #speckit #spec-kit #task-analysis #classify #workflow-selection #tinyspec

Ready to run

npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-tinyspec-classify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-tinyspec-classify
Source: https://github.com/opsmill/infrahub-mcp/tree/main/.agents/skills/speckit-tinyspec-classify
Command: npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-tinyspec-classify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify a given task description to decide whether to apply the tinyspec workflow or the full SDD workflow, helping teams choose the most efficient path and preventing scope creep.

Core Features & Use Cases

Automatically analyze task descriptions to detect complexity signals for small and large tasks.
Recommend the appropriate workflow (tinyspec vs. speckit.specify) and provide a clear plan for next steps.
Help project teams align on scope, reduce miscommunication, and accelerate decision-making across product and engineering.

Quick Start

Describe a task you want to work on, and I will classify its complexity and recommend tinyspec or full SDD workflow.

Frequently Asked Questions about speckit-tinyspec-classify

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

FAQPage Schema

How do I choose between tinyspec and SDD for my spec-kit task?▼

To choose between tinyspec and SDD, classify the task description to evaluate its scope and complexity, which outputs a recommended workflow path and corresponding guidance for your project.

What is the best way to prevent scope creep in spec-kit projects?▼

The best way to prevent scope creep is to classify task complexity early, routing small tasks to tinyspec and large tasks to the full SDD workflow for appropriate alignment.

Does the tinyspec classifier work without a .specify directory?▼

No, the tinyspec classifier requires a spec-kit project containing a .specify directory to analyze the task description and recommend the appropriate SDD workflow path.

How do I analyze task complexity to route work to the correct SDD workflow?▼

Analyze task complexity by providing a task description to the classifier, which detects complexity signals and outputs a clear plan recommending either the tinyspec or full SDD workflow.

When should I use full SDD instead of tinyspec for task analysis?▼

Use full SDD instead of tinyspec when the classifier detects large task scope and high complexity signals, ensuring the work receives the detailed guidance required by the full SDD workflow.

Why does my spec-kit project need workflow selection for task descriptions?▼

Spec-kit projects need workflow selection to align product and engineering teams on scope, reduce miscommunication, and accelerate decision-making by routing tasks to the most efficient workflow path.