implementation-routing

Classify TypeScript tasks by scope and delegate to framework-specific implementers.

2|Updated Mar 1, 2026

Search Tags:#typescript #routing #delegation #frontend-backend #requirements-clarification #architecture-planning

Ready to run

npx skills add https://github.com/nholder88/ai-agent-workflows --skill implementation-routing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-routing
Source: https://github.com/nholder88/ai-agent-workflows/tree/main/skills/implementation-routing
Command: npx skills add https://github.com/nholder88/ai-agent-workflows --skill implementation-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route TypeScript and mixed-scope implementation tasks to the correct specialist by classifying backend vs frontend vs full-stack scope, identifying framework, and delegating to the right implementer.

Core Features & Use Cases

Route mixed TypeScript work to appropriate implementer (impl-* skills) based on scope and framework.
Detect frontend framework by inspecting project metadata (package.json, tsconfig.json) and delegate to Next.js, SvelteKit, Angular, or generic frontend implementers.
Support multi-stage task splitting and coordination across backend and frontend streams with proper contracts and reviews.

Quick Start

Provide a TypeScript task description and I will route it to the appropriate implementation path.

Frequently Asked Questions about implementation-routing

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

FAQPage Schema

How do I route TypeScript tasks to the right frontend or backend implementer?▼

Routing TypeScript tasks involves analyzing project context such as package.json and tsconfig.json to classify backend, frontend, or full-stack scope, then delegating to the appropriate specialist implementer.

Can I split full-stack TypeScript requirements for parallel implementation?▼

Yes, full-stack TypeScript tasks can be split into multi-stage streams, enabling parallel backend and frontend implementation while preserving contracts to coordinate reviews across both paths.

Does the router detect specific frontend frameworks like Next.js or SvelteKit?▼

Yes, it inspects package.json and tsconfig.json to detect specific frameworks like Next.js, SvelteKit, and Angular, delegating tasks to the matching implementer or a generic frontend specialist.

What is the best way to delegate mixed-scope TypeScript implementation work?▼

The best way is to classify the task scope, identify the frontend framework from project metadata, and route requirements to specialized implementers while preserving contracts for parallel execution.

Do I need a package.json file to use the TypeScript task router?▼

Providing package.json and tsconfig.json is necessary for accurate routing, as the router analyzes this project context to determine the framework and appropriate delegation paths.