backend-implement

Implement backend features using test-driven development and git worktree isolation.

3|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/KeyValueSoftwareSystems/maestro --skill backend-implement-keyvaluesoftwaresystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-implement
Source: https://github.com/KeyValueSoftwareSystems/maestro/tree/main/skills/core/sdlc/backend-implement
Command: npx skills add https://github.com/KeyValueSoftwareSystems/maestro --skill backend-implement-keyvaluesoftwaresystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates inconsistent coding practices and scope creep by enforcing a strict, deterministic, test-first workflow for backend development that ensures every change meets rigorous engineering standards.

Core Features & Use Cases

  • Contract-First Implementation: Ensures backend code strictly adheres to published contracts, preventing silent API drift.
  • Automated Workflow Enforcement: Guides the agent through git worktree isolation, task DAG execution, and mandatory human gates for sensitive operations.
  • Use Case: When implementing a new microservice endpoint, use this skill to automatically fan out tasks into slices, enforce TDD, and verify compliance with security, idempotency, and observability standards before merging.

Quick Start

Invoke the backend-implement skill to begin the implementation of the approved backend scope defined in the current task manifest.

Frequently Asked Questions about backend-implement

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

FAQPage Schema
How do I enforce test-driven development for backend implementation?

To enforce test-driven development for backend implementation, use a strict deterministic workflow that mandates writing tests first and validates all changes against comprehensive engineering standards before merging.

What is contract testing and how does it prevent API drift in backend services?

Contract testing verifies that backend code strictly adheres to published contracts, preventing silent API drift by ensuring every implemented endpoint matches the agreed-upon service interface specifications.

How do I isolate backend development tasks using git worktrees?

Isolate backend development tasks using git worktrees to manage complex execution, allowing parallel slice processing and dependency-ordered task DAGs without interfering with the main branch.

Does this test-first workflow support security and observability requirements?

Yes, this test-first workflow validates all backend changes against comprehensive engineering standards, explicitly checking security, backward compatibility, idempotency, and observability requirements before any merge occurs.

How do I manage complex backend task execution with dependency-ordered slices?

Manage complex backend task execution by fanning out approved scope into dependency-ordered slices, processing each sequentially through a task DAG while enforcing mandatory human gates for sensitive operations.

When do I need automated workflow enforcement for backend engineering standards?

You need automated workflow enforcement when inconsistent coding practices and scope creep risk undermining backend development, requiring strict TDD cycles and contract adherence to maintain code quality.