Use when user asks "is the workflow actually working", "are we deferring too much", "what's our profile mix", "did the impact bar help", "how many follow-ups did this epic file", "what's the codex auto-fix rate", or any other meta-question about pm-vibecode-ops execution patterns. Also use when about to count Linear comments by hand to answer one of those questions, when about to grep .swarm/observability/*.jsonl directly, when reviewing a recently-closed epic for sprawl, or when investigating why a ticket halted. Also use when about to recommend a workflow change based on intuition rather than the observability stream.
$npx -y skills add bdouble/pm-vibecode-ops --skill swarm-observabilityInstalls into the current project.
Run `npx skills use "https://github.com/bdouble/pm-vibecode-ops" --skill "bdouble/pm-vibecode-ops/swarm-observability"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/bdouble/pm-vibecode-ops" that are relevant to the current task. Run `npx skills add "https://github.com/bdouble/pm-vibecode-ops"` and select the relevant skills, then follow their instructions.