# Orchestrate Full-Stack Feature Delivery

Complex features require coordinated decisions across data, APIs, interfaces, tests, and operations. This skill organizes delivery into connected phases with clear outputs and validation.

## Install

```bash
npx skillstore add sickn33/full-stack-orchestration-full-stack-feature
```

## Metadata

- Status: approved
- Slug: sickn33-full-stack-orchestration-full-stack-feature
- Skillstore revision: r2
- Version status: missing
- Tree hash: 00975e941ac55602ac3e2d9b89ad130aebbb65a7bda39c1fae31c85500bf56f3
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/full-stack-orchestration-full-stack-feature
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- 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
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-full-stack-orchestration-full-stack-feature
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-full-stack-orchestration-full-stack-feature/manifest

## Capabilities

- Plans database, backend, and frontend architecture in a dependency-aware sequence.
- Defines API contracts before coordinating backend and frontend implementation.
- Organizes backend, frontend, and database implementation tasks for parallel delivery.
- Specifies contract, integration, end-to-end, load, and visual regression testing.
- Includes security review, deployment infrastructure, observability, and performance optimization phases.
- Accepts stack, deployment, feature flag, API, testing, and compliance preferences.

## Use Cases

- Plan a New Product Feature: Create a phased delivery plan that connects schemas, APIs, interfaces, tests, and deployment requirements.
- Coordinate Parallel Implementation: Divide approved architecture into backend, frontend, and database work that converges through shared contracts.
- Prepare a Production Rollout: Add security, infrastructure, observability, performance, feature flags, and rollback planning before release.

## Prompt Templates

### Create a Feature Plan

```
Plan a full-stack feature for [goal]. Use [stack], identify missing requirements, and define outputs for each delivery phase.
```

### Design Contracts and Components

```
Design the database, API contract, backend services, and frontend components for [feature]. Include authentication, validation, accessibility, and migration requirements.
```

### Coordinate Implementation and Testing

```
Orchestrate implementation of [feature] across backend, frontend, and database work. Define contract, integration, end-to-end, load, and security tests.
```

### Plan an Advanced Production Rollout

```
Prepare [feature] for [deployment target] under [compliance standard]. Include CI/CD gates, observability, performance targets, feature flags, rollback, and ownership.
```

## Limitations

- It provides orchestration instructions, not a standalone executable workflow.
- Named subagent types require compatible Task tool support or manual adaptation.
- Generated implementations still require environment-specific testing, permissions, and expert review.
- The referenced detailed implementation playbook is not included in this package.

## Best Practices

- Resolve requirements, constraints, ownership, and success metrics before starting architecture.
- Keep database, API, frontend, and test artifacts traceable to the same approved requirements.
- Verify security, performance, observability, and rollback behavior in the target environment before release.

## Anti Patterns

- Do not begin parallel implementation before approving shared data and API contracts.
- Do not treat generated infrastructure or security guidance as validated production configuration.
- Do not declare completion without contract tests, critical user journeys, monitoring, and rollback evidence.

## Security Audit

- Audited at: 2026-07-23T23:09:26.065\+00:00
- Summary: All seven static findings are false positives caused by Markdown inline code around a resource path and configuration names. The skill contains no shell execution instructions or semantic security threats.

## Stats

- Views: 153
- Downloads: 8
- Favorites: 1
- Popularity score: 0