ring:pre-dev-feature

Plan and execute a 5-gate pre-dev workflow for small features.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/LucasMalessa/TheRing --skill ring-pre-dev-feature-lucasmalessa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ring:pre-dev-feature
Source: https://github.com/LucasMalessa/TheRing/tree/main/pm-team/skills/pre-dev-feature
Command: npx skills add https://github.com/LucasMalessa/TheRing --skill ring-pre-dev-feature-lucasmalessa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Small feature teams often struggle with starting a feature in a disciplined, lightweight process that still ensures alignment with architecture and product goals.

Core Features & Use Cases

  • 5-gate pre-dev workflow designed for features that take under 2 days to implement
  • Orchestrates topology discovery, research, PRD creation with UX validation, design validation, TRD, task breakdown, and delivery planning
  • Provides a standardized, human-approval gated process to reduce rework and miscommunication

Quick Start

Describe and map your feature into the pre-dev track by collecting inputs for topology, research, PRD, UX criteria (if UI), TRD, tasks, and a delivery plan, then begin the gate sequence.

Frequently Asked Questions about ring:pre-dev-feature

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

FAQPage Schema
What is a pre-dev workflow and why do I need gates for small features?

A pre-dev workflow establishes a clear, gated path before coding begins. You need gates for small features to ensure alignment with architecture and product goals, reducing rework and miscommunication through standardized approvals.

How do I plan a pre-dev workflow for a feature that takes under 2 days to implement?

Plan a pre-dev workflow by mapping your feature into a 5-gate sequence: topology discovery, research, PRD creation with UX validation, design validation, TRD, task breakdown, and delivery planning to produce structured artifacts and approvals.

Can I use this 5-gate pre-dev workflow for features without a UI?

Yes, you can use this pre-dev workflow without a UI. The process includes UX validation criteria conditionally, allowing you to skip UI-specific steps and proceed directly through TRD, task breakdown, and delivery planning gates.

What is the best way to structure PRD and TRD creation for lightweight feature planning?

The best way to structure PRD and TRD creation is through a sequential gated process. You create the PRD with UX validation first, then proceed to design validation and TRD creation, ensuring technical requirements align with product goals before delivery planning.

Do I need any specific tools or dependencies to run this pre-dev planning process?

No specific tools or dependencies are required to run this pre-dev planning process. It is a lightweight workflow that orchestrates topology discovery, research, and document creation to establish clear governance and handoff without external dependencies.

When should I not use a lightweight 5-gate pre-dev workflow?

You should not use a lightweight 5-gate pre-dev workflow for large features exceeding 2 days of implementation. It is specifically designed for small features requiring a disciplined but lightweight alignment process rather than comprehensive enterprise governance.