taw-new

Forward preset-based taw-new requests to the main /taw workflow.

32|13|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-new
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taw-new
Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/taw-new
Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-new

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

taw-new provides a backward-compatible shim that forwards preset-based calls to the main /taw workflow, ensuring existing users and automation keep working during upgrades.

Core Features & Use Cases

  • Maintains compatibility with older taw-kit versions by routing to /taw with the BUILD branch
  • Forwards preset args unchanged, enabling seamless migration paths
  • Provides a simple fallback path for users who still invoke taw-new while upgrading

Quick Start

Run taw-new with a preset name to automatically forward to /taw and start the preset scaffolding.

Frequently Asked Questions about taw-new

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

FAQPage Schema
How do I maintain backward compatibility when routing preset-based requests to a new workflow?

To maintain backward compatibility, you can use a shim that forwards preset-based requests to the main workflow. This ensures existing automation keeps working by routing calls with a preset prefix to the appropriate build path.

What is a shim routing approach for legacy build preset workflows?

A shim routing approach for build presets forwards legacy requests to a main workflow path. It intercepts calls and applies a preset prefix to the arguments, enabling seamless migration across different kit versions.

How do I forward arguments with a preset prefix during a workflow migration?

You forward arguments with a preset prefix by passing them through a compatibility shim. The shim routes the unchanged arguments to the target workflow, allowing the main process to load the correct build preset path.

Can I use a fallback routing path for older kit versions without breaking automation?

Yes, you can use a fallback routing path for older kit versions without breaking automation. A compatibility shim intercepts legacy calls and forwards them to the main workflow, ensuring existing processes continue functioning.

When do I need a backward-compatible shim for build preset scaffolding?

You need a backward-compatible shim for build preset scaffolding when upgrading workflows while supporting older kit versions. It provides a simple fallback path, allowing users to invoke legacy commands while leveraging the main workflow.