dev-implementation

Automate Gate 0 code implementation with TDD and agent selection.

205|26|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/LerianStudio/ring --skill dev-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-implementation
Source: https://github.com/LerianStudio/ring/tree/main/dev-team/skills/dev-implementation
Command: npx skills add https://github.com/LerianStudio/ring --skill dev-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate 0 of the development cycle is automated by selecting the right agent, applying TDD, and documenting decisions.

Core Features & Use Cases

  • Language-aware agent selection (Go/TS/Python)
  • TDD-first workflow: RED-GREEN-REFACTOR
  • Handoff to next gates with implementation details

Quick Start

Kick off Gate 0 of a feature using the appropriate language and service type; review the Implementation Summary.

Frequently Asked Questions about dev-implementation

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

FAQPage Schema
How do I automate code implementation with test-driven development across Go, TypeScript, and Python?

Test-driven development automates code implementation by selecting language-aware agents that execute the RED-GREEN-REFACTOR cycle, validate against PROJECT_RULES.md standards, and handle service types (api, worker, batch, cli, frontend, bff) across Gate 0 of your development workflow.

What languages and service types does automated code implementation support?

Automated code implementation supports Go, TypeScript, and Python across six service types: api, worker, batch, cli, frontend, and bff. Language-aware agent selection ensures implementation follows type-specific patterns and project standards during Gate 0.

How does TDD-first workflow improve code handoff between development gates?

TDD-first workflow executes RED-GREEN-REFACTOR cycles that validate functional and technical requirements, document implementation decisions in markdown sections (Implementation Summary, TDD Results, Files Changed), and package results as structured handoff to the next gate.

Can I enforce project coding standards automatically during implementation?

Yes. The implementation process validates input schemas (unit_id, requirements, language, service_type) and enforces PROJECT_RULES.md standards through agent selection and verification steps, ensuring consistent code patterns across your codebase during Gate 0.

What input information do I need to provide for automated code implementation?

Required inputs are unit_id, requirements, language, and service_type. Optional inputs include technical_design, existing_patterns, and project_rules_path. These parameters route to the correct language-aware agent and configure TDD execution during Gate 0.

Does automated implementation work with existing code patterns and design decisions?

Yes. Optional fields for existing_patterns and technical_design parameters allow the implementation agent to preserve your codebase conventions and apply decisions consistently, ensuring new code integrates seamlessly with current architecture.