Skip to content
Back to skills

Using Pm Team

ASecurity

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.

  • 215 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
developmentgoapi

Works with

  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add LerianStudio/ring --skill using-pm-team --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Using Pm Team?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Using Pm Team
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lerianstudio-using-pm-team/badge)](https://www.skillsdirectory.com/skills/lerianstudio-using-pm-team)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ring:using-pm-team
description: |
  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.
---

# Using Ring Team-Product: Pre-Dev Workflow & Delivery Tracking

## 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 12 pre-development planning skills and 4 research 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.

## Two Tracks: Choose Your Path

### Small Track (5 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:pre-dev-research | research.md |
| 1 | ring:pre-dev-prd-creation | prd.md |
| 2 | ring:pre-dev-trd-creation | trd.md |
| 3 | ring:pre-dev-task-breakdown | tasks.md |
| 4 | ring:pre-dev-delivery-planning | delivery-roadmap.md + .json |

**Planning time:** 60-90 minutes

### Large Track (10 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:pre-dev-research | research.md |
| 1 | ring:pre-dev-prd-creation | prd.md |
| 1.5 | ring:pre-dev-design-validation | design-validation.md (if UI) |
| 2 | ring:pre-dev-feature-map | feature-map.md |
| 2.5 | ring:pre-dev-design-validation | design-validation.md (if UI, Large) |
| 3 | ring:pre-dev-trd-creation | trd.md |
| 4 | ring:pre-dev-api-design | api-design.md |
| 5 | ring:pre-dev-data-model | data-model.md |
| 6 | ring:pre-dev-dependency-map | dependencies.md |
| 7 | ring:pre-dev-task-breakdown | tasks.md |
| 8 | ring:pre-dev-subtask-creation | subtasks/ |
| 9 | ring:pre-dev-delivery-planning | delivery-roadmap.md + .json |

**Planning time:** 2.5-5 hours

## Gate Summaries

| Gate | Skill | What It Does |
|------|-------|-------------|
| 0 | ring:pre-dev-research | Parallel research: codebase patterns, best practices, framework docs |
| 1 | ring:pre-dev-prd-creation | Business requirements (WHAT/WHY), user stories, success metrics |
| 1.5/2.5 | ring:pre-dev-design-validation | UX completeness check: screens, states, responsive, a11y |
| 2 | ring:pre-dev-feature-map | Feature relationships, dependencies, deployment order (Large only) |
| 3 | ring:pre-dev-trd-creation | Technical architecture, technology-agnostic patterns |
| 4 | ring:pre-dev-api-design | API contracts, operations, error handling (Large only) |
| 5 | ring:pre-dev-data-model | Entities, relationships, ownership (Large only) |
| 6 | ring:pre-dev-dependency-map | Explicit tech choices, versions, licenses (Large only) |
| 7 | ring:pre-dev-task-breakdown | Value-driven tasks with success criteria |
| 8 | ring:pre-dev-subtask-creation | Zero-context 2-5 min implementation steps (Large only) |
| 9/4 | ring:pre-dev-delivery-planning | Realistic schedule with critical path + JSON output |

## Standalone Skills

| Skill | When to Use |
|-------|-------------|
| ring:deep-doc-review | Before dev-cycle to catch doc contradictions |
| ring:delivery-status | Progress tracking against approved roadmap |
| ring:streaming-event-mapping | 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 |

## Research Agents (dispatched by Gate 0)

| Agent | Specialization |
|-------|---------------|
| ring:repo-research-analyst | Codebase patterns, existing solutions |
| ring:best-practices-researcher | External best practices, industry standards |
| ring:framework-docs-researcher | Tech stack docs, version constraints |
| ring:product-designer | UX research, personas, competitive analysis |

## Entry Points

- **Small Track:** Invoke `ring:pre-dev-feature`
- **Large Track:** Invoke `ring:pre-dev-full`
- **Specific gate:** Invoke the gate's skill directly if prior gates are done

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.