taw-add

Forward legacy taw-add invocations to the /taw command.

32|13|Updated Apr 21, 2026

Search Tags:#routing #cli #backward-compatibility #legacy #shim #taw

Ready to run

npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-add

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: taw-add
Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/taw-add
Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DEPRECATED — use /taw instead. This shim forwards to /taw with the BUILD branch (add-feature path). Kept for backward compatibility with earlier taw-kit versions.

Core Features & Use Cases

Backward-compatibility shim that forwards to /taw for legacy feature additions.
Sunset plan: Removed in a future version. Users should switch to /taw thêm <feature> or /taw add <feature>.

Quick Start

Invoke taw-add to forward to taw using the compat shim.

Frequently Asked Questions about taw-add

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

FAQPage Schema

How do I maintain backward compatibility for legacy cli routing when updating my workflow?▼

A backward-compatible shim maintains legacy cli routing by automatically forwarding deprecated invocations to the main command, ensuring older setup configurations continue functioning during sunset migration without breaking changes.

What is a compatibility shim and how does it work for legacy command forwarding?▼

A compatibility shim is a minimal wrapper that intercepts legacy command invocations and forwards them to a new primary command path, allowing deprecated setups to trigger feature additions seamlessly while transitioning to updated workflows.

Do I need a shim wrapper to handle legacy invocations if I already use the main command?▼

No, you do not need a shim wrapper if you already use the main command directly. The shim exists solely to support legacy setups, and users on current versions should invoke the primary command to trigger feature additions.

What is the best way to migrate from a deprecated cli command to a new routing path?▼

The best way to migrate from a deprecated cli command is to switch directly to the main command's updated invocation syntax for feature additions, as the legacy shim wrapper is scheduled for removal in a future sunset plan.

Why does my legacy taw-add invocation still trigger feature additions?▼

Your legacy taw-add invocation still triggers feature additions because a backward-compatible shim intercepts the call and forwards it to the main taw command using the add-feature path, ensuring forward compatibility during sunset migration.