/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
$ npx -y skills add LerianStudio/ring --skill using-pm-team --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/using-pm-team
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
using-pm-team.SKILL.mdname: ring:using-pm-team
description: "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 starting a feature that needs systematic planning. Skip for quick exploratory work, known-solution bug fixes, or trivial changes."
Using Ring PM-Team: Pre-Dev Workflow
When to use
- Starting any feature implementation
- Need systematic planning before coding
- User requests "plan a feature"
Skip when
- Quick exploratory work → skip formal planning
- Bug fix with known solution → direct implementation
- Trivial change (<1 hour) → skip formal planning
The ring-pm-team plugin provides 14 skills and 4 agents. Use them via `Skill tool: "ring:gate-name"`.
Follow the **ORCHESTRATOR principle** from `ring:using-ring`. Dispatch pre-dev workflow to handle planning; plan thoroughly before coding.
All artifacts land in `docs/pre-dev/<feature-name>/`. Both tracks end at `plan.md` — the single execution document consumed by `ring:running-dev-cycle` and `ring:executing-plans`.
Two Tracks: Choose Your Path
Small Track (4 Gates) — <2 Day Features
Use when ALL criteria met: implementation <2 days, no new external dependencies, no new data models, no multi-service integration, uses existing architecture, single developer.
| Gate | Skill | Output | |------|-------|--------| | 0 | ring:researching-features | research.md | | 1 | ring:writing-prds | prd.md | | 2 | ring:writing-trds | trd.md | | 3 | ring:writing-plans (invoked by orchestrator) | plan.md |
Large Track (8 Gates) — ≥2 Day Features
Use when ANY criteria met: implementation ≥2 days, new external dependencies, new data models/entities, multi-service integration, new architecture patterns, team collaboration needed.
| Gate | Skill | Output | |------|-------|--------| | 0 | ring:researching-features | research.md | | 1 | ring:writing-prds | prd.md | | 2 | ring:mapping-feature-relationships | feature-map.md | | 3 | ring:writing-trds | trd.md | | 4 | ring:designing-api-contracts | openapi.yaml | | 5 | ring:designing-data-model | schema.sql / schema.prisma (stack-native) | | 6 | ring:pinning-dependency-versions | dependencies.md | | 7 | ring:writing-plans (default plugin, invoked by orchestrator) | plan.md |
Gate Summaries
| Gate | Skill | What It Does | |------|-------|-------------| | 0 | ring:researching-features | Parallel technical/product research: codebase patterns, web research (firecrawl/exa), framework docs | | 1 | ring:writing-prds | Squad-facing product spec: what, why, scope, functional requirements, acceptance criteria | | 2 | ring:mapping-feature-relationships | Feature relationships, dependencies, and the phasing the squad validates (Large only) | | 3 | ring:writing-trds | Technical architecture: components, boundaries, data flow, integration points | | 4 | ring:designing-api-contracts | Real OpenAPI 3.1 spec: paths, schemas, error envelope (Large only) | | 5 | ring:designing-data-model | Real stack-native schema: DDL, indexes, constraints (Large only) | | 6 | ring:pinning-dependency-versions | Explicit tech choices, versions, licenses (Large only) | | 7/3 | ring:writing-plans | Rolling-wave phased plan: all phases with epics, Phase 1 detailed into tasks |
Standalone Utilities
| Skill | When to Use | |-------|-------------| | ring:validating-ux-completeness | Before the TRD when the feature has UI; validates ux-criteria/wireframes from a product-designer run | | ring:mapping-streaming-events | Map eventable points in Go service for lib-streaming | | ring:creating-grafana-dashboards | Sweep telemetry → telemetry-dictionary.md → PM iterates themes → Grafonnet dashboards + blocking drift CI | | ring:reconciling-predev-docs | Before dev-cycle to catch contradictions across pre-dev artifacts |
Agents
| Agent | Specialization | |-------|---------------| | ring:repo-researcher | Codebase patterns, existing solutions (Gate 0) | | ring:web-researcher | External best practices, industry standards (Gate 0) | | ring:docs-researcher | Tech stack docs, version constraints (Gate 0) | | ring:product-designer | Standalone UX step (ux-research, ux-validation, ux-design) — not a gate agent |
Entry Points
- **Small Track:** Invoke `ring:planning-small-features`
- **Large Track:** Invoke `ring:planning-large-features`
- **Specific gate:** Invoke the gate's skill directly if prior gates are done
Read more
name: ring:using-pm-team description: "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 starting a feature that needs systematic planning. Skip for quick exploratory work, known-solution bug fixes, or trivial changes."
Using Ring PM-Team: Pre-Dev Workflow
When to use
- Starting any feature implementation
- Need systematic planning before coding
- User requests "plan a feature"
Skip when
- Quick exploratory work → skip formal planning
- Bug fix with known solution → direct implementation
- Trivial change (<1 hour) → skip formal planning
The ring-pm-team plugin provides 14 skills and 4 agents. Use them via `Skill tool: "ring:gate-name"`.
Follow the **ORCHESTRATOR principle** from `ring:using-ring`. Dispatch pre-dev workflow to handle planning; plan thoroughly before coding.
All artifacts land in `docs/pre-dev/<feature-name>/`. Both tracks end at `plan.md` — the single execution document consumed by `ring:running-dev-cycle` and `ring:executing-plans`.
Two Tracks: Choose Your Path
Small Track (4 Gates) — <2 Day Features
Use when ALL criteria met: implementation <2 days, no new external dependencies, no new data models, no multi-service integration, uses existing architecture, single developer.
| Gate | Skill | Output | |------|-------|--------| | 0 | ring:researching-features | research.md | | 1 | ring:writing-prds | prd.md | | 2 | ring:writing-trds | trd.md | | 3 | ring:writing-plans (invoked by orchestrator) | plan.md |
Large Track (8 Gates) — ≥2 Day Features
Use when ANY criteria met: implementation ≥2 days, new external dependencies, new data models/entities, multi-service integration, new architecture patterns, team collaboration needed.
| Gate | Skill | Output | |------|-------|--------| | 0 | ring:researching-features | research.md | | 1 | ring:writing-prds | prd.md | | 2 | ring:mapping-feature-relationships | feature-map.md | | 3 | ring:writing-trds | trd.md | | 4 | ring:designing-api-contracts | openapi.yaml | | 5 | ring:designing-data-model | schema.sql / schema.prisma (stack-native) | | 6 | ring:pinning-dependency-versions | dependencies.md | | 7 | ring:writing-plans (default plugin, invoked by orchestrator) | plan.md |
Gate Summaries
| Gate | Skill | What It Does | |------|-------|-------------| | 0 | ring:researching-features | Parallel technical/product research: codebase patterns, web research (firecrawl/exa), framework docs | | 1 | ring:writing-prds | Squad-facing product spec: what, why, scope, functional requirements, acceptance criteria | | 2 | ring:mapping-feature-relationships | Feature relationships, dependencies, and the phasing the squad validates (Large only) | | 3 | ring:writing-trds | Technical architecture: components, boundaries, data flow, integration points | | 4 | ring:designing-api-contracts | Real OpenAPI 3.1 spec: paths, schemas, error envelope (Large only) | | 5 | ring:designing-data-model | Real stack-native schema: DDL, indexes, constraints (Large only) | | 6 | ring:pinning-dependency-versions | Explicit tech choices, versions, licenses (Large only) | | 7/3 | ring:writing-plans | Rolling-wave phased plan: all phases with epics, Phase 1 detailed into tasks |
Standalone Utilities
| Skill | When to Use | |-------|-------------| | ring:validating-ux-completeness | Before the TRD when the feature has UI; validates ux-criteria/wireframes from a product-designer run | | ring:mapping-streaming-events | Map eventable points in Go service for lib-streaming | | ring:creating-grafana-dashboards | Sweep telemetry → telemetry-dictionary.md → PM iterates themes → Grafonnet dashboards + blocking drift CI | | ring:reconciling-predev-docs | Before dev-cycle to catch contradictions across pre-dev artifacts |
Agents
| Agent | Specialization | |-------|---------------| | ring:repo-researcher | Codebase patterns, existing solutions (Gate 0) | | ring:web-researcher | External best practices, industry standards (Gate 0) | | ring:docs-researcher | Tech stack docs, version constraints (Gate 0) | | ring:product-designer | Standalone UX step (ux-research, ux-validation, ux-design) — not a gate agent |
Entry Points
- **Small Track:** Invoke `ring:planning-small-features`
- **Large Track:** Invoke `ring:planning-large-features`
- **Specific gate:** Invoke the gate's skill directly if prior gates are done
Proven engineering practices, enforced through skills. Ring is a comprehensive skills library and workflow system for AI agents that transforms how AI assistants approach software development.
Repo: LerianStudio/ring
Other skills on ring.
- /analyzing-options
Analyzing different approaches for a task or problem with structured comparisons, effort estimates, and recommendations. Use when facing strategic decisions, architecture choices, or multiple viable approaches. Skip when there's an obvious single approach or the decision is
Open skill - /auditing-production-readiness
Auditing a service's production readiness against Ring engineering standards across base dimensions plus a conditional multi-tenant dimension, then emitting a scored report and an HTML dashboard. Use before production deploy, periodic review, onboarding, or a major release. Skip
Open skill - /cleaning-comments
Cleaning redundant and obvious comments following clean code principles while preserving meaningful documentation. Supports git scope filtering (staged, unstaged, branch, commit-range). Use when code has excessive comments, during code review, or post-refactor cleanup. Skip when
Open skill - /committing-changes
Commit changes with scope allowlist enforcement, atomic grouping, GPG-signed conventional commits, and trailer management. Detects the repo's PR-validation scope policy before proposing any message. Use when the user asks to commit or has changes ready to record. Skip when the
Open skill - /creating-handoffs
Creating a handoff document that captures session state (completed work, decisions, open items, next steps) and delivering it via Plan Mode so the user gets the native 'clear context and continue implementing' resume option. Use when ending a session, when context grows large,
Open skill - /creating-worktrees
Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from
Open skill