handle

Name: handle
Availability: InStock
Author: i-standard1

Classify development requests and route them to appropriate workflows.

6|2|Updated Apr 5, 2026

Search Tags:#workflow #planning #github #handoff #spec #triage #requests

Ready to run

npx skills add https://github.com/i-standard1/yamasaki --skill handle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handle
Source: https://github.com/i-standard1/yamasaki/tree/main/.claude/skills/handle
Command: npx skills add https://github.com/i-standard1/yamasaki --skill handle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a universal intake for development requests, triaging and routing them to the most effective workflow to keep projects on track.

Core Features & Use Cases

Classifies requests (questions, investigations, feature requests, bug reports, and operational tasks) and maps them to the appropriate action or follow-up.
Supports hands-off handoffs to downstream tasks (documentation, implementation, or review) and tracks status across teams.
Use Case: When a user says "handle this bug" or "review this feature request", the Skill suggests the next steps and routes the task to the right process.

Quick Start

Instruct the agent to accept any incoming development request and triage it to the appropriate workflow.

Frequently Asked Questions about handle

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

FAQPage Schema

How do I triage and route incoming development requests across teams?▼

To triage development requests, you can use a universal intake workflow that classifies questions, investigations, and bug reports, then maps them to the appropriate downstream actions and structured handoffs across teams.

What is the best way to automate GitHub issue handling and classification?▼

Automating GitHub issue handling involves routing each issue to the most effective workflow, enforcing classification rules, and generating structured handoffs to map actions for downstream implementation or review tasks.

Can I route feature requests and bug reports to different downstream workflows?▼

Yes, you can route feature requests and bug reports to different workflows by enforcing classification rules that map each specific request type to the most appropriate downstream implementation, documentation, or review process.

Does this request routing approach work for operational tasks and general codebase questions?▼

Yes, this request routing approach works for operational tasks and general codebase questions by classifying all incoming inquiries and mapping them to the appropriate action, follow-up, or structured handoff.

What are the limitations of using automated request triage for project planning?▼

Automated request triage for project planning maps actions and generates handoffs but does not execute the downstream implementation itself, requiring separate processes to complete the actual development or review tasks.