Tw93
f163734ddc
Align README and packaged dispatcher guidance with explicitly authorized workflows. Shorten two skill summaries while preserving the README structure and personal voice.
2.5 KiB
name, description
| name | description |
|---|---|
| waza | Dispatcher for Waza engineering skills: think (architecture/handoff), ui (artifact-grounded interface design), check (review/release gates), hunt (runtime debugging/regression), write (prose/release copy), learn (research), read (URL/PDF fetch), health (agent config and AI maintainability audit). |
Waza: Engineering Skills Dispatcher
Prefix your first line with 🥷 inline, not as its own paragraph.
You have eight skills available. Match the user's intent to the right skill, read the matching section below, and execute it.
Routing Table
How This Works
- Read the user's message and match it to a skill from the table above.
- Read the matched skill section in full.
- Execute that skill's instructions exactly.
If the message could match multiple skills, use these disambiguation rules:
- Most specific wins:
/uiis more specific than/thinkfor UI decisions. - URL in message: start with
/read. If the content is research material, chain to/learn. - Code already done vs. code broken: done/PR ->
/check; error/broken ->/hunt. - Config/maintainability vs. code: Codex/Claude misbehaving, hooks/MCP,
/healthtoken usage, AI coding code rot, unclear context, missing verification, or stale verifier output ->/health; user code errors ->/hunt. - Release action vs. release prose: commit/tag/publish/push/release reactions/close issue ->
/check; write release notes/changelog text ->/write. - Screenshot taste vs. screenshot regression: visual taste complaint ->
/ui; broken render/state/generated output or used-to-work evidence ->/hunt. - From scratch vs. editing: new long-form output ->
/learn; existing draft to polish ->/write. - "Judge this" + error ->
/hunt; "judge this" + should we keep it ->/think. - Still ambiguous: read both skills' "Not for" sections; use exclusion. If still unclear, ask the user.
Path Resolution
In this distribution, sub-skill scripts live at skills/{name}/scripts/. Resolve all relative paths from this file's directory, not from a personal home-directory skill cache.
Chaining
Each skill stops at the requested outcome. If the user explicitly authorizes a workflow across skills, complete that workflow without asking for approval at every transition; do not infer authorization for further actions.
Common chains: /think -> implement approved plan -> /check | /hunt -> fix -> /check -> release/push/issue follow-through | /read -> /learn -> /write