ring-using-pm-team

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