AI Agent Workflow Collection

Use when creating, reviewing, or migrating telemetry pipelines that collect, transform, route, buffer, validate, and deliver logs, metrics, traces, events, or profiles across tool-agnostic observability systems.

Use when a product idea, business problem, platform initiative, strategy item, or vague roadmap request needs customer outcome framing, value stream boundaries, flow steps, measures, and first capability candidates.

Write, reply to, and resolve Google Drive comments on Docs, Sheets, Slides, and Drive files with evidence-backed location context.

Use when architecture boundaries, integrations, ownership, containers, components, deployment, dependencies, or stakeholder communication need C4-style views tied to value streams, capabilities, features, stories, or implementation plans.

Use when building platform or application observability, defining SLOs, preparing telemetry backend artifacts, enforcing OpenTelemetry semantic conventions, creating alert dashboards, or migrating SRE rules.

Use when an idea, initiative, architecture change, roadmap item, epic, or vague product request needs to become a coherent pipeline of value stream, capability, feature, story, architecture, spec, plan, implementation, and verification artifacts.

Use when value stream, capability, feature, story, C4, spec, or implementation-plan artifacts need a coherence check before execution, especially when context has grown large or architectural intent may be lost.

Use when a capability, epic, roadmap item, or architecture change needs feature-sized delivery packets with acceptance criteria, NFRs, enablers, dependencies, C4 impact, and story-slicing readiness.

Use when a feature or implementation-ready slice needs to become a human-sized story packet, acceptance tests, enabler work, spec handoff, implementation-plan input, and execution context without overwhelming the user.