software-engineer

Implement backend services and APIs from specifications with error handling.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ouakar/ubinarys-dental --skill software-engineer-ouakar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-engineer
Source: https://github.com/ouakar/ubinarys-dental/tree/main/skills/forgewright/skills/software-engineer
Command: npx skills add https://github.com/ouakar/ubinarys-dental --skill software-engineer-ouakar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

[production-grade internal] Implements backend services, APIs, and business logic — builds features, fixes bugs, refactors code from specs. Includes error handling, idempotency, concurrency, and clean architecture patterns. Routed via the production-grade orchestrator.

Core Features & Use Cases

  • Implements robust back-end services from specifications
  • Applies clean architecture, error handling, and idempotency across services
  • Refactors, tests, and ships features reliably under orchestration

Quick Start

Provide a production-grade backend feature specification and I will implement it end-to-end.

Frequently Asked Questions about software-engineer

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

FAQPage Schema
How do I implement production-grade backend services from a feature specification?

Production-grade backend services are implemented end-to-end from specifications by applying clean architecture patterns, robust error handling, idempotency, and concurrency control across modular architectures.

What is the best way to ensure idempotency and concurrency control in backend APIs?

Idempotency and concurrency control in backend APIs are ensured by applying production-grade architecture patterns during feature implementation, refactoring, and bug fixing from specifications.

Can I use this approach to refactor and fix bugs across modular architectures?

Refactoring and fixing bugs across modular architectures is fully supported, applying clean architecture patterns and robust error handling to ensure services remain production-grade.

Does building production-grade services require a specific orchestrator setup?

Building production-grade services is routed via a production-grade orchestrator, which aligns clean architecture, error handling, and idempotency patterns across the implemented backend services.

How do I ship backend features reliably with proper error handling and testing?

Backend features are shipped reliably by implementing robust error handling and testing from specifications, ensuring the codebase remains aligned with a production-grade orchestrator.

When should I not use a clean architecture approach for backend services?

Clean architecture for backend services should be avoided when the task lacks clear modular boundaries or when the scale does not require strict idempotency, concurrency control, and error handling.