waldo.BCTelemetryBuddy

Spec authoring workflow for BC Telemetry Buddy (SDD Phase 0). Takes a GitHub issue number, drafts a behavior spec with acceptance criteria under docs/specs/, and gates the TDD cycle. Use when: picking up a feature/bug/tech-modernization issue, before any plan or code. Not for knowledge-base issues (use /kb-article-creation).

Knowledge Base article creation workflow for BC Telemetry Buddy. Automates: GitHub issue intake → validation prompt generation → article creation from validated report → index regeneration → issue closure. Use when: creating new KB articles from GitHub issues, validating telemetry event schemas, writing playbooks/query-patterns/event-interpretations.

Test-Driven Development workflow for BC Telemetry Buddy. Enforces the PLAN → FRAME → TESTS → PROVE RED → SCAFFOLD → IMPLEMENT → VERIFY → SECURITY SCAN → DOCUMENT cycle. Requires an approved spec (SDD Phase 0 — /spec-authoring) before the PLAN phase. Use when: adding features, fixing bugs, refactoring code, implementing new MCP tools, extension commands, or shared-lib modules. Mandatory before any code change.

Release one or both components (extension + MCP) with version bumps, CHANGELOG updates, git tags, and push

Security scan for BC Telemetry Buddy. Invoked from Phase 8 of the TDD workflow and before any release. Scans for real tenant GUIDs, bearer tokens, AAD secrets, customer identifiers in fixtures/snapshots/logs, untracked secret files, and high/critical npm audit findings. A finding BLOCKS the cycle — never "note and continue". Use when: finishing a TDD cycle, preparing a release, reviewing a PR, or any time before code leaves the machine.