using-pm-team
10 pre-dev workflow skills + 3 research agents organized into Small Track (4 gates, <2 days) andLarge Track (9 gates, 2+ days) for systematic feature planning with research-first approach.
When & Why to Use This Skill
The ring:using-pm-team skill is a comprehensive pre-development workflow framework designed to automate and systematize software feature planning. By integrating 10 specialized planning skills and 3 research agents, it enforces a 'plan-first' philosophy through structured 'Small' and 'Large' tracks. This skill ensures that developers have clear requirements, sound architecture, and atomic task breakdowns before implementation, significantly reducing technical debt and scope creep.
Use Cases
- Complex Feature Planning: Utilize the 9-gate Large Track for major features involving new data models, external dependencies, or multi-service integrations to ensure architectural integrity.
- Automated Technical Documentation: Rapidly generate standardized PRDs, TRDs, API contracts, and dependency maps to maintain a clear 'source of truth' for the development team.
- Deep Technical Research: Deploy specialized agents to analyze existing codebase patterns and framework documentation to find the best implementation path before coding starts.
- Granular Task Decomposition: Transform high-level feature requests into atomic, 2-5 minute implementation steps with explicit success criteria to streamline the execution phase.
| name | ring:using-pm-team |
|---|---|
| description | | |
| trigger | | |
| skip_when | | |
| - Quick exploratory work → ring | brainstorming may suffice |
Using Ring Team-Product: Pre-Dev Workflow
The ring-pm-team plugin provides 10 pre-development planning skills and 3 research agents. Use them via Skill tool: "ring:gate-name" or via slash commands.
Remember: Follow the ORCHESTRATOR principle from ring:using-ring. Dispatch pre-dev workflow to handle planning; plan thoroughly before coding.
Pre-Dev Philosophy
Before you code, you plan. Every time.
Pre-dev workflow ensures:
- ✅ Requirements are clear (WHAT/WHY)
- ✅ Architecture is sound (HOW)
- ✅ APIs are contracts (boundaries)
- ✅ Data models are explicit (entities)
- ✅ Dependencies are known (tech choices)
- ✅ Tasks are atomic (2-5 min each)
- ✅ Implementation is execution, not design
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: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 |
Planning time: 45-75 minutes
Large Track (9 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 |
| 2 | ring:pre-dev-feature-map | feature-map.md |
| 3 | ring:pre-dev-trd-creation | TRD.md |
| 4 | ring:pre-dev-api-design | API.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/ |
Planning time: 2.5-4.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 |
| 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) |
Research Agents (Gate 0)
| Agent | Focus |
|---|---|
ring:repo-research-analyst |
Codebase patterns, docs/solutions/ knowledge base |
ring:best-practices-researcher |
Web search, Context7 for best practices |
ring:framework-docs-researcher |
Tech stack versions, official patterns |
Research Modes:
- greenfield: Web research primary (new capability)
- modification: Codebase research primary (extending existing)
- integration: All agents equally weighted (connecting systems)
Using Pre-Dev Workflow
Via Slash Commands
/ring:pre-dev-feature logout-button # Small track (4 gates)
/ring:pre-dev-full payment-system # Large track (9 gates)
Via Skills (Manual)
Skill tool: "ring:pre-dev-prd-creation"
(Review output)
Skill tool: "ring:pre-dev-trd-creation"
(Review output)
Output Structure
docs/pre-dev/{feature}/
├── research.md # Gate 0
├── prd.md # Gate 1
├── feature-map.md # Gate 2 (large only)
├── trd.md # Gate 3
├── api-design.md # Gate 4 (large only)
├── data-model.md # Gate 5 (large only)
├── dependency-map.md # Gate 6 (large only)
├── tasks.md # Gate 7
└── subtasks/ # Gate 8 (large only)
Decision: Small or Large Track?
When in doubt: Use Large Track. Better to over-plan than discover mid-implementation that feature is larger.
You can switch: If Small Track feature grows, pause and complete Large Track gates.
Integration with Other Plugins
| Plugin | Use For |
|---|---|
| ring:using-ring (default) | ORCHESTRATOR principle for ALL tasks |
| ring:using-dev-team | Developer specialists for reviewing designs |
| ring:using-finops-team | Regulatory compliance planning |
| ring:using-tw-team | Documentation for features |
Combined with:
ring:execute-plan– Run tasks in batchesring:write-plan– Generate plan from scratch*-engineer– Specialist review of designring:requesting-code-review– Post-implementation review
ORCHESTRATOR Principle
- You're the orchestrator – Dispatch pre-dev skills, don't plan manually
- Don't skip gates – Each gate adds clarity
- Don't code without planning – Plan first, code second
- Use agents for specialist review – Dispatch engineers to review TRD
Good (ORCHESTRATOR):
"I need to plan payment system. Let me run /ring:pre-dev-full, then dispatch ring:backend-engineer-golang to review the architecture."
Bad (OPERATOR):
"I'll start coding and plan as I go."