Claude Skills by LerianStudio

Dual-mode skill for github.com/LerianStudio/lib-observability/tracing — OpenTelemetry SDK lifecycle, trace context propagation across HTTP/gRPC/queues, span error and event recording, and struct-to-attribute conversion with PII redaction. Sweep Mode dispatches parallel explorers to find raw OTEL setup, hand-rolled header propagation, manual span attribute assembly, DIY redaction, and untraced boundaries. Reference Mode catalogs the API (Telemetry, TelemetryConfig, Redactor, propagation helper...

Author Grafana dashboards for Lerian Go services rooted in real lib-observability telemetry (tracing, metrics, log, constants). Three phases — Sweep (telemetry inventory), Iterate (PM deliberation on SLIs/SLOs and alerts), Author (Grafonnet libsonnet → JSON in CI) — and installs a blocking CI drift gate. Use when scaffolding dashboards, building a telemetry dictionary, or auditing observability. Skip if service is non-Go, emits no telemetry, or task is just folder organization.

Deep review of project documentation before entering dev-cycle. Finds errors, inconsistencies, gaps, missing data, and contradictions across PRD, TRD, API design, data model, and other pre-dev artifacts. Cross-references information between docs — not just reviewing one doc in isolation — to catch mismatches that cause implementation failures.

Delivery status tracking and progress reporting. Analyzes repository against delivery roadmap to calculate actual vs planned progress, identify delays, and provide insights on velocity and risk trends.

Gate 4: API contracts document - defines component interfaces and data contracts before protocol/technology selection. Large Track only.

Gate 5: Data structures document - defines entities, relationships, and ownership before database technology selection. Large Track only.

Gate 9 (Full Track) / Gate 4 (Small Track): Delivery roadmap and timeline planning. Transforms tasks into realistic delivery schedule with critical path analysis, resource allocation, and delivery breakdown. MANDATORY gate for both workflows.

Gate 6: Technology choices document - explicit, versioned, validated technology selections with justifications. Large Track only. HARD BLOCK: Must load Ring Standards and PROJECT_RULES.md before proceeding.

Gate 1.5/2.5: Design Validation - verifies UX specifications are complete before proceeding to technical architecture. Checklist-based validation that prevents incomplete designs from reaching implementation.

Gate 2: Feature relationship map - visualizes feature landscape, groupings, and interactions at business level before technical architecture.

Lightweight 5-gate pre-dev workflow for small features (<2 days). Orchestrates topology discovery, research, PRD with UX validation, design validation, TRD, task breakdown, and delivery planning in a sequential gated process with human approval at each gate.

Complete 10-gate pre-dev workflow for large features (>=2 days). Orchestrates topology discovery, research, PRD, feature map, design validation, TRD, API design, data model, dependency map, task breakdown, subtask creation, and delivery planning in a sequential gated process with human approval at each gate.

Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.

Gate 0 research phase for pre-dev workflow. Dispatches 4 parallel research agents to gather codebase patterns, external best practices, framework documentation, and UX/product research BEFORE creating PRD/TRD. Outputs research.md with file:line references and user research findings.

Gate 8: Zero-context implementation steps - 2-5 minute atomic subtasks with complete code, exact commands, TDD pattern. Large Track only.

Gate 7 (Full Track) / Gate 3 (Small Track): Implementation tasks - value-driven decomposition into working increments that deliver measurable user value.

Gate 3 (Full Track) / Gate 2 (Small Track): Technical architecture document - defines HOW/WHERE with technology-agnostic patterns before concrete implementation choices.

Identify "eventable points" in a Lerian Go service where lib-streaming should emit business events to per-tenant SaaS subscribers. Three passes (Survey, Slice, Mark) produce a PM-validated event catalog (Markdown) and instrumentation map (JSON) for ring:dev-streaming-instrumentation. Enforces the past-tense durable tenant-scoped scope fence and CRITICAL/IMPORTANT/OBSERVATIONAL/CUSTOM postures. Skip on non-Go, infra-only, or consumer-only services.

12 pre-dev workflow skills + 2 standalone discovery skills + 1 standalone dashboard skill + 4 research agents organized into Small Track (5 gates, <2 days) and Large Track (10 gates, 2+ days) for systematic feature planning with research-first approach.

Patterns for organizing and structuring documentation including hierarchy, navigation, and information architecture.

Comprehensive checklist and process for reviewing documentation quality including voice, tone, structure, completeness, and technical accuracy.

Technical writing specialists for functional and API documentation. Dispatch when you need to create guides, conceptual docs, or API references following established documentation standards.

Voice and tone guidelines for technical documentation. Ensures consistent, clear, and human writing across all documentation.

Patterns and structure for writing API reference documentation including endpoint descriptions, request/response schemas, and error documentation.

Patterns and structure for writing functional documentation including guides, conceptual explanations, tutorials, and best practices documentation.