ring:pre-dev-feature

Automate a four-gate pre-development workflow for small software features.

4|Updated Jan 10, 2026

Search Tags:#documentation #PRD #feature-development #TRD #pre-dev #gated-workflow #gate-automation

Ready to run

npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-feature

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ring:pre-dev-feature
Source: https://github.com/LerianStudio/ring-for-opencode/tree/main/assets/skill/pre-dev-feature
Command: npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes the early-stage feature delivery process by providing a concise four-gate pre-development workflow for small features that can be completed quickly.

Core Features & Use Cases

Gate 0: Research phase with 3 research agents running in parallel to surface patterns and risks.
Gate 1: PRD creation capturing problem statements, user value, acceptance criteria, and success metrics.
Gate 2: TRD creation mapping PRD features to architecture components in a technology-agnostic way.
Gate 3: Task breakdown detailing value-driven tasks with dependencies and testing strategies.
Artifacts are saved under docs/pre-dev/<feature-name> to enable repeatable execution and review.

Quick Start

Create the directory docs/pre-dev/<feature-name>, then run the ring:pre-dev-feature workflow to guide gates 0-3 and generate artifacts.

Frequently Asked Questions about ring:pre-dev-feature

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

FAQPage Schema

How do I automate pre-development documentation for small software features?▼

You can automate pre-development documentation using a gated workflow that guides research, PRD creation, TRD creation, and task breakdown, saving artifacts under docs/pre-dev/<feature-name>.

What is the best way to structure PRD and TRD creation for a quick feature?▼

The best way to structure PRD and TRD creation is through a four-gate workflow where Gate 1 captures problem statements and acceptance criteria, while Gate 2 maps features to architecture components.

Can I use this gated pre-dev workflow for large multi-week projects?▼

No, this gated pre-dev workflow is designed specifically for small software features that can be completed in under two days, enforcing lightweight criteria for quick delivery.

How does the task breakdown phase work in a feature development workflow?▼

The task breakdown phase works by detailing value-driven tasks with explicit dependencies and testing strategies, serving as the final gate before development begins.

Do I need human approval between documentation gates?▼

Yes, you need human approval between gates because the workflow prompts for manual validation after the research, PRD, TRD, and task breakdown phases to enforce gate criteria.

What happens during the research phase of a pre-development feature workflow?▼

During the research phase, three research agents run in parallel to surface patterns and risks, establishing the foundational context before PRD creation begins.