ring:using-pm-team

Name: ring:using-pm-team
Availability: InStock
Author: LucasMalessa

Orchestrate gate-based pre-development workflows and generate planning artifacts.

Updated Mar 21, 2026

Search Tags:#workflow #planning #governance #artifacts #product-management #pre-dev #feature-planning

Ready to run

npx skills add https://github.com/LucasMalessa/TheRing --skill ring-using-pm-team-lucasmalessa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ring:using-pm-team
Source: https://github.com/LucasMalessa/TheRing/tree/main/pm-team/skills/using-pm-team
Command: npx skills add https://github.com/LucasMalessa/TheRing --skill ring-using-pm-team-lucasmalessa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline and orchestrate pre-development planning for feature delivery by coordinating a defined gate-based workflow and artifact generation.

Core Features & Use Cases

ORCHESTRATES a gate-driven planning process that covers both Small Track (<2 days) and Large Track (2+ days) with outputs such as research.md, PRD.md, TRD.md, tasks.md, and delivery-roadmap.md.
Dispatches specialized research and planning agents via slash commands or Skill tools to produce structured artifacts before coding.
Provides governance and guardrails, ensuring artifacts exist and gates are followed before implementation.

Quick Start

Invoke the pre-dev workflow to generate initial planning artifacts for a feature.

Frequently Asked Questions about ring:using-pm-team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is gate-driven pre-development planning for feature delivery?▼

Gate-driven pre-development planning coordinates structured artifact creation and governance checks before coding begins, enforcing workflow gates to produce research, PRD, and TRD documents that streamline feature delivery for product teams.

How do I generate pre-dev planning artifacts like PRD and TRD for a new feature?▼

To generate pre-dev planning artifacts, invoke the orchestrator workflow to dispatch specialized research and planning agents. This coordinates the creation of research.md, PRD.md, TRD.md, tasks.md, and delivery-roadmap.md through defined governance gates before implementation.

Does pre-dev workflow planning support small track features under two days?▼

Yes, pre-dev workflow planning supports Small Track features estimated under two days alongside Large Track workflows for features spanning two or more days, applying appropriate governance gates and artifact generation requirements to both tracks.

Can I enforce governance and guardrails before feature implementation starts?▼

Yes, the ORCHESTRATOR workflow enforces governance and guardrails by ensuring required planning artifacts exist and gates are completed before implementation begins, providing strict coordination across feature planning workflows for product teams.

What is the best way to orchestrate research and PRD generation for product management?▼

The best way to orchestrate research and PRD generation is using a gate-driven workflow that dispatches specialized planning agents via slash commands, ensuring structured artifact creation and governance before development starts on feature work.

When should I not use a gate-based pre-development planning workflow?▼

A gate-based pre-development planning workflow may be unnecessary for trivial changes or urgent hotfixes where formal artifact generation and governance gates would slow delivery below the Small Track threshold of two days for feature work.