Ring PM Team

Plugin ring-pm-team from marketplace ring in LerianStudio/ring. Commands read from the repo's manifest — 12 days ago.

Skills (14)

• ring:creating-grafana-dashboards

  Authoring Grafana dashboards for Go services instrumented with lib-observability telemetry (tracing, metrics, log), plus a reference mode for RED/USE panel patterns and Grafonnet templates. Sweep mode inventories telemetry, runs PM deliberation on themes/SLIs/alerts, authors Grafonnet libsonnet comp

• ring:designing-api-contracts

  Designing the API contract as a real OpenAPI 3.1 specification (openapi.yaml with full paths, operations, schemas, components, Lerian error envelope, and auth schemes) from the validated TRD. Gate 4 of ring:planning-large-features, Large Track only; runs after ring:writing-trds, before ring:designin

• ring:designing-data-model

  Designing the physical data model as a real stack-native schema (schema.sql with CREATE TABLE DDL, indexes, and constraints for Postgres/Go; schema.prisma for Prisma/TS; Postgres schema.sql as fallback) from the Gate 4 OpenAPI spec and TRD. Gate 5 of ring:planning-large-features; runs after ring:des

• ring:mapping-feature-relationships

  Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs afte

• ring:mapping-streaming-events

  Mapping the eventable points in a Lerian Go service where lib-streaming should emit past-tense, durable, tenant-scoped business events, producing a PM-validated event catalog and instrumentation-map.json for ring:instrumenting-streaming-events. Three-pass discovery (Survey, Slice, Mark) with a scope

• ring:pinning-dependency-versions

  Pinning an explicit versioned dependency manifest (dependencies.md plus PROJECT_RULES.md): exact package versions, CVE and license checks, compatibility matrices, and per-component cost analysis against Ring Standards. Gate 6 of ring:planning-large-features; runs after ring:designing-data-model, bef

• ring:planning-large-features

  Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use r

• ring:planning-small-features

  Planning the lightweight 4-gate Small Track pre-dev workflow (research, PRD, TRD, plan) with human approval and state tracking at each gate. Use for features under 2 days that reuse existing patterns and add no new dependencies, data models, or services. Skip for larger or complex features — use rin

• ring:reconciling-predev-docs

  Reconciling pre-dev artifacts (research.md, prd.md, feature-map.md, trd.md, openapi.yaml, schema file, dependencies.md, plan.md) against each other to surface contradictions and gaps that break implementation, then applying approved corrections before ring:running-dev-cycle. Use after ring:planning-

• ring:researching-features

  Researching the product/feature in depth before any planning document is written: the product itself, technical approach, third-party integrations, prior art, and existing codebase grounding (file:line refs) via parallel repo/web/docs agents using firecrawl and exa. Gate 0 of ring:using-pm-team (bot

• ring:using-pm-team

  Routing feature planning through the ring-pm-team pre-dev workflow: choosing the Small Track (4 gates, <2 days) or Large Track (8 gates, 2+ days) and entering via ring:planning-small-features or ring:planning-large-features. Indexes pre-dev gates, standalone utilities, and research agents. Use when

• ring:validating-ux-completeness

  Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a p

• ring:writing-prds

  Writing a Product Requirements Document that explains to the squad WHAT is being built and WHY: problem, explicit scope in/out, functional requirements, and testable acceptance criteria. Gate 1 of ring:using-pm-team; runs after ring:researching-features and stays technology-free (no architecture, fr

• ring:writing-trds

  Writing a Technical Requirements Document that designs the technical architecture of the system or feature: components and boundaries, data flow, integration points, failure modes, and the mandatory program structure (DDD/hexagonal source tree) — in technology-agnostic patterns (code structure excep

Subagents (4)

• ring:docs-researcher

  Tech stack analysis specialist for pre-dev planning. Detects project tech stack from manifest files, then uses firecrawl (scrape/crawl) and exa to fetch official framework/library documentation. Identifies version constraints and implementation patterns from official docs.

• ring:product-designer

  Product Designer agent for UX research, user validation, and design specifications. Accepts feature context and research findings. Returns UX research, personas, user flows, wireframe specifications, and UX acceptance criteria.

• ring:repo-researcher

  Codebase research specialist for pre-dev planning. Searches target repository for existing patterns, conventions, and prior solutions. Returns findings with exact file:line references for use in PRD/TRD creation.

• ring:web-researcher

  External research specialist for pre-dev planning. Uses firecrawl (search/scrape/crawl) and exa to find industry best practices, prior art, open source examples, and authoritative guidance. Primary agent for greenfield features where codebase patterns don't exist.

Hooks (2)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh

Similar plugins