ring:pre-dev-trd-creation

Name: ring:pre-dev-trd-creation
Availability: InStock
Author: LucasMalessa

Define technology-agnostic architecture decisions and gating before technology selection.

Updated Mar 21, 2026

Search Tags:#architecture #gates #tech-stack #project-rules #design-validation #trd

Ready to run

npx skills add https://github.com/LucasMalessa/TheRing --skill ring-pre-dev-trd-creation-lucasmalessa

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to establish technology-agnostic architectural decisions (HOW/WHERE) before selecting concrete products, preventing vendor lock-in and misaligned implementations.

Core Features & Use Cases

Enforces Gate-based TRD workflows (Gate 0/1/2/3) with explicit criteria.
Promotes architecture patterns over specific technologies (modular monolith, microservices, etc.) and defines interfaces.
Provides templates and checklists to align data ownership, security, and integration patterns before tech choices.
Use Case: A cross-team project defines architecture first, then selects Go or TS stacks without rework.

Quick Start

Define technology-agnostic architecture goals and gating criteria, and validate architecture before selecting concrete technologies.

Frequently Asked Questions about ring:pre-dev-trd-creation

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

FAQPage Schema

What is technology-agnostic architecture gating in a TRD workflow?▼

Technology-agnostic architecture gating establishes HOW/WHERE design decisions and validates data ownership, security, and integration patterns before selecting specific tech stacks. This prevents vendor lock-in and implementation rework.

How do I define architecture decisions before selecting a tech stack?▼

Define architecture by selecting patterns like modular monolith or microservices over specific technologies, establishing interfaces, and applying Gate 3 prerequisites to validate design completeness independently of products.

When do I need technology-agnostic architecture patterns for project rules?▼

You need technology-agnostic architecture patterns for cross-team projects where you must define architecture first, allowing later tech selection like Go or TS stacks without causing implementation rework.

Can I validate data ownership and security planning before choosing technologies?▼

Yes, you validate data ownership and security planning before choosing technologies by using architecture templates and checklists that enforce completeness and agnostic patterns independent of specific products.

Does the Gate 3 TRD workflow support multiple domains?▼

Yes, the Gate 3 TRD workflow supports multiple domains by scoping TRD guidance across prerequisites, design validation, and architecture templates to ensure comprehensive architecture completeness across project areas.

What are the limitations of selecting products before defining architecture gates?▼

Selecting products before defining architecture gates causes vendor lock-in and misaligned implementations, requiring rework when the chosen technology fails to fit required agnostic patterns and data ownership rules.