ai-boardlisted

# Board ## Quick start ``` /ai-board discover # one-time configuration discovery /ai-board discover --refresh # force re-discovery /ai-board sync in_progress #45 # transition GitHub issue /ai-board sync in_review AB#100 # transition Azure Boards work item ``` ## Subcommands `/ai-board` carries two subcommands that previously lived as separate skills (`/ai-board discover` and `/ai-board sync` — collapsed in spec-127 D-127-10 to a single skill with subcommand routing). | Subcommand | Detail file | Purpose | | ---------- | ----------- | ------- | | `discover` | [`discover.md`](discover.md) | Post-install discovery of board configuration (fields, state mappings, process templates) — writes atomically to `manifest.yml`. | | `sync` | [`sync.md`](sync.md) | Lifecycle state transitions on the project board (`refinement` → `ready` → `in_progress` → `in_review` → `done`). Auto-invoked by `/ai-brainstorm`, `/ai-build`, and `/ai-pr`. Fail-open: never blocks the calling workflow. | ## Workflow The skill body owns the user-facing routing contract. Detail files own the per-subcommand procedure. Step 0 (load contexts): read `.ai-engineering/manifest.yml` `providers.stacks`; load `.ai-engineering/overrides/<stack>/conventions.md` for each stack and `.ai-engineering/overrides/_shared/conventions.md`; load `.ai-engineering/team/*.md` for team conventions. 1. Detect subcommand from the first positional argument. 2. If `disc