asc-workflow

# asc workflow Use this skill when you need lane-style automation inside the CLI using: - `asc workflow run` - `asc workflow validate` - `asc workflow list` This feature is best for deterministic automation that lives in your repo, is reviewable in PRs, and can run the same way locally and in CI. ## Command discovery - Always use `--help` to confirm flags and subcommands: - `asc workflow --help` - `asc workflow run --help` - `asc workflow validate --help` - `asc workflow list --help` ## End-to-end flow 1. Author `.asc/workflow.json` 2. Validate structure and references: - `asc workflow validate` 3. Discover available workflows: - `asc workflow list` - `asc workflow list --all` (includes private helpers) 4. Preview execution without side effects: - `asc workflow run --dry-run beta` 5. Execute with runtime params: - `asc workflow run beta BUILD_ID:123456789 GROUP_ID:abcdef` ## File location and format - Default path: `.asc/workflow.json` - Override path: `asc workflow run --file ./path/to/workflow.json <name>` - JSONC comments are supported (`//` and `/* ... */`) ## Output and CI contract - `stdout`: structured JSON result (`status`, `steps`, durations) - `stderr`: step command output, hook output, dry-run previews - `asc workflow validate` always prints JSON and returns non-zero when invalid This enables machine-safe checks: ```bash asc workflow validate | jq -e '.valid == true' asc workflow run beta BUILD_ID:123 GROUP_ID:xyz | jq -e '.status...