# Orchestrate Complete Backend Feature Delivery

Complex backend features often fail when requirements, architecture, testing, and rollout work remain disconnected. This skill coordinates twelve delivery phases with defined outputs, controls, and handoffs.

## Install

```bash
npx skillstore add sickn33/backend-development-feature-development
```

## Metadata

- Status: approved
- Slug: sickn33-backend-development-feature-development
- Skillstore revision: r2
- Version status: missing
- Tree hash: faed0609c79521557d77d2604a934a596c5cb89c3188d42dbe87907f39b4aa52
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/backend-development-feature-development
- Ref: 5a26d1d61d694db29af9b138c661c1981076d9df
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-backend-development-feature-development
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-backend-development-feature-development/manifest

## Capabilities

- Transforms a feature brief into user stories, acceptance criteria, success metrics, dependencies, and risks.
- Defines service boundaries, API contracts, data models, integration points, and security requirements.
- Coordinates backend, frontend, and data implementation through specialized agents and shared phase context.
- Plans unit, integration, end-to-end, performance, and security testing with measurable quality targets.
- Prepares feature flags, gradual rollout, monitoring, rollback procedures, and production documentation.
- Supports traditional, TDD, BDD, and DDD methodologies across four feature complexity levels.

## Use Cases

- Plan a Cross-Service Feature: Turn a product request into requirements, architecture, ownership, dependencies, risks, and measurable delivery criteria.
- Coordinate Technical Implementation: Align backend, frontend, and data work through shared contracts, staged outputs, and integrated testing.
- Prepare a Controlled Rollout: Define deployment gates, feature flags, observability, rollback actions, and operational documentation before release.

## Prompt Templates

### Create a Feature Plan

```
Plan a medium backend feature for [feature]. Use TDD and feature flags. Define requirements, architecture, tests, rollout, monitoring, and rollback outputs.
```

### Coordinate Multiple Services

```
Coordinate delivery of [feature] across [services]. Identify dependencies, API and data changes, ownership, security checks, acceptance criteria, and a canary deployment plan.
```

### Design a Domain Workflow

```
Design a DDD workflow for [feature] in [domain]. Define bounded contexts, aggregates, contracts, migration stages, testing layers, observability, and rollback controls.
```

### Orchestrate an Epic Rollout

```
Orchestrate an epic for [feature] across [teams and systems]. Include phased ownership, compliance gates, performance budgets, data migration, canary metrics, incident thresholds, and rollback decisions.
```

## Limitations

- Requires compatible specialist agents for the complete twelve-phase workflow.
- Does not replace environment-specific testing, security review, or production approval.
- Creates unnecessary overhead for small isolated changes and routine bug fixes.
- Depends on clear scope, constraints, permissions, and success criteria from the user.

## Best Practices

- Provide current architecture, owners, constraints, and measurable success criteria before starting discovery.
- Review each phase output before passing it to implementation or deployment agents.
- Validate migrations, feature flags, monitoring, and rollback procedures in staging before production approval.

## Anti Patterns

- Do not use the complete workflow for a small isolated fix.
- Do not deploy generated changes without environment-specific testing and human approval.
- Do not proceed when scope, permissions, safety boundaries, or success criteria remain unclear.

## Security Audit

- Audited at: 2026-08-14T09:37:09.497\+00:00
- Summary: The only static finding is a false positive because SKILL.md line 35 requires approvals and rollback plans before production changes. No evidence of reconnaissance, prompt injection, exfiltration, or malicious intent was found.

## Stats

- Views: 115
- Downloads: 12
- Favorites: 0
- Popularity score: 0