work-type-classifier

Classify user requests into predefined work types and output .claude/auto-context.yaml.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/adiomas/claude-code-adiomas-plugins --skill work-type-classifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-type-classifier
Source: https://github.com/adiomas/claude-code-adiomas-plugins/tree/main/autonomous-dev/skills/work-type-classifier
Command: npx skills add https://github.com/adiomas/claude-code-adiomas-plugins --skill work-type-classifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the classification of development requests into predefined work types so Claude can select and orchestrate the appropriate set of domain-specific and discipline skills.

Core Features & Use Cases

  • Layered keyword and intent detection across FRONTEND, BACKEND, FULLSTACK, RESEARCH, DOCUMENTATION, and CREATIVE signals.
  • Automatic confidence scoring and decision making, with optional user confirmation when uncertain.
  • Generates a .claude/auto-context.yaml payload describing detected keywords, intents, and recommended skills for execution.

Quick Start

Example: Provide a sample request like 'Add a webhook endpoint for payments' to observe the generated auto-context.yaml with work_type and suggested skills.

Frequently Asked Questions about work-type-classifier

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

FAQPage Schema
How do I automatically classify development requests into frontend or backend work types?

It categorizes development requests into work types by analyzing input keywords, intents, and output expectations, covering FRONTEND, BACKEND, FULLSTACK, RESEARCH, DOCUMENTATION, and CREATIVE domains.

How does intent detection work for routing autonomous development tasks?

Intent detection for autonomous development tasks works by analyzing request signals across multiple layers and scoring confidence to trigger the correct domain-specific skills, prompting user confirmation only when confidence is low.

How do I generate an auto-context.yaml file with recommended skills for my project?

You generate an auto-context.yaml file by submitting a development request like 'Add a webhook endpoint for payments'; the skill outputs a structured payload describing detected keywords, intents, work type, and recommended skills.

Can I use this work type classifier for fullstack and research tasks?

Yes, you can use this work type classifier for fullstack and research tasks, as it explicitly evaluates layered signals across FRONTEND, BACKEND, FULLSTACK, RESEARCH, DOCUMENTATION, and CREATIVE categories to orchestrate appropriate skills.

What happens when keyword analysis confidence is low during request classification?

When keyword analysis confidence is low during request classification, the system triggers an optional user confirmation step to verify the detected work type before generating the final auto-context.yaml payload.