add-command

# Add Command Scaffold a new command definition inside an existing addon or framework. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "I need a new command" → scaffold command in specified target - "build a slash command" → scaffold with slash-command template - "add a flow command" → scaffold with orchestration template - "new CLI command for X" → derive name, prompt for target ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Named add | "add command lint-fix --to aiwg-utils" | Scaffold directly | | Template specified | "add command deploy-all --template orchestration" | Use named template | | Interactive | "add command --interactive --to sdlc-complete" | Guided mode | | Target omitted | "add command my-command" | Ask which addon or framework | ## Process ### 1. Parse Arguments Extract from `$ARGUMENTS`: - `<name>` — kebab-case command name (required) - `--to <target>` — addon or framework directory name (required) - `--template <type>` — one of `utility` (default), `transformation`, `orchestration` - `--interactive` — enable guided design questions If either `<name>` or `--to` is missing, ask before proceeding. ### 2. Understand the Command Model Commands in AIWG are generated from skills at deploy time. The primary source of truth is the skill definition; the command file is the deployable artifact. This skill scaffolds the comma...