ring:dev-implementation

This skill executes the implementation phase of the development cycle: • Selects the appropriate specialized agent based on task content • Applies project standards from docs/PROJECT_RULES.md • Follows TDD methodology (RED → GREEN → REFACTOR) • Documents implementation decisions

<block_condition> • PROJECT_RULES.md does not exist at project_rules_path </block_condition> If condition is true, STOP and return error to orchestrator. `text • Check PROJECT_RULES.md exists: Read tool → project_rules_path (default: docs/PROJECT_RULES.md) if not found: → STOP with blocker: "Cannot implement without project standards" → Return error to orchestrator • Select implementation agent based on language: | Language | Service Type | Agent | |----------|--------------|-------| | go | api, worker, batch, cli | ring:backend-engineer-golang | | typescript | api, worker | ring:backend-engineer-typescript | | typescript | frontend, bff | frontend-bff-engineer-typescript | Store: selected_agent = [agent name] `

This skill ORCHESTRATES. Agents IMPLEMENT. | Who | Responsibility | |-----|----------------| | This Skill | Select agent, prepare prompts, track state, validate outputs | | Implementation Agent | Write tests, write code, follow standards | ---

<verify_before_proceed> • unit_id exists • requirements exists • language is valid (go|typescript|python) • service_type is valid (api|worker|batch|cli|frontend|bff) </verify_before_proceed> `text REQUIRED INPUT (from ring:dev-cycle orchestrator): • unit_id: [task/subtask being implemented] • requirements: [acceptance criteria or task description] • language: [go|typescript|python] • service_type: [api|worker|batch|cli|frontend|bff] OPTIONAL INPUT: • technical_design: [path to design doc] • existing_patterns: [patterns to follow] • project_rules_path: [default: docs/PROJECT_RULES.md] if any REQUIRED input is missing: → STOP and report: "Missing required input: [field]" → Return to orchestrator with error `