feature-delivery

Coordinate end-to-end feature delivery from planning through verified implementation and release handoff.

Updated May 8, 2026

Search Tags:#planning #qa #release #orchestration #end-to-end #feature-delivery #security-review

Ready to run

npx skills add https://github.com/ace3/skills --skill feature-delivery-ace3

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-delivery
Source: https://github.com/ace3/skills/tree/main/skills/feature-delivery
Command: npx skills add https://github.com/ace3/skills --skill feature-delivery-ace3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Feature requests often stall in planning, coordination, and handoffs across multiple specialties. This skill batches planning, implementation, QA, security review, and release steps into a single end-to-end workflow, reducing handoff friction and speeding delivery.

Core Features & Use Cases

End-to-end orchestration: from planning through implementation, QA, and release handoff.
Built-in governance: explicit gates to prevent destructive actions and ensure compliance.
Evidence-driven finish: collects artifacts and outputs under standardized delivery contracts.

Quick Start

Trigger the feature-delivery run with a single command to start end-to-end delivery.

Frequently Asked Questions about feature-delivery

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

FAQPage Schema

How do I orchestrate end-to-end feature delivery from planning to release?▼

End-to-end feature delivery orchestration coordinates planning, implementation, QA, security review, and release handoff in a single workflow, reducing manual invocation of multiple specialists. It batches these steps to minimize handoff friction and speed up the overall delivery process.

Can I enforce governance gates for destructive actions during feature release?▼

Yes, feature delivery workflows enforce governance through explicit gates that prevent destructive actions and ensure compliance. These built-in controls mandate minimal surgical changes and require reproducible evidence before proceeding to release handoff.

What is the best way to automate security review and QA in a feature delivery pipeline?▼

Automating security review and QA involves batching granular testing and security checks into a unified delivery orchestration workflow. This approach eliminates manual specialist invocation and ensures evidence-driven finish via standardized output contracts.

Do I need multiple specialists for planning, implementation, and release handoff?▼

No, a single end-to-end feature delivery workflow replaces the need for manually invoking multiple specialists. It coordinates planning, implementation, tests, granular QA, security review, and release handoff automatically through a single triggered run.

How does evidence-driven finish work for feature delivery?▼

Evidence-driven finish collects artifacts and outputs under standardized delivery contracts at the end of the feature delivery workflow. This ensures reproducible evidence for governance requirements and facilitates standardized handoffs across the pipeline.

When should I use an end-to-end feature delivery orchestration workflow?▼

Use end-to-end feature delivery orchestration when a user needs coordinated planning, implementation, tests, granular QA, security review, and release handoff. It is ideal for satisfying governance requirements for minimal surgical changes and reproducible evidence without manual specialist coordination.