skills.rest
Rosetears520
Rosetears520COMMUNITY
Explore all skills by this author →
GitHub

aili-delivery-flow

Orchestrate IDEATE, DEFINE, BUILD, and SHIP lifecycle modes with backend-aware artifact routing.

2|Updated May 3, 2026
Search Tags:#build automation#test planning#release readiness#backend routing#lifecycle orchestration#evidence gates#spec authoring
One-click install
npx skills add https://github.com/Rosetears520/aili-workflows --skill aili-delivery-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aili-delivery-flow
Source: https://github.com/Rosetears520/aili-workflows/tree/main/skills/aili-delivery-flow
Command: npx skills add https://github.com/Rosetears520/aili-workflows --skill aili-delivery-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It provides a unified, rule-driven delivery lifecycle for turning an idea into specs/tests and then into verified implementation and release closeout—without exposing internal stage commands.

Core Features & Use Cases

  • Mode-gated lifecycle orchestration: enforce IDEATE/DEFINE/BUILD/SHIP boundaries and stop when mandatory approvals, artifacts, or evidence are missing.
  • Backend-aware artifact routing: select and apply an appropriate backend adapter (OpenSpec, plan-based, custom files, or conservative auto-detection) while preserving lifecycle gates.
  • Verification-first progress: require fresh verification evidence, support Unverified labels only when explicitly accepted/waived, and block on unresolved release-blocking findings.
  • Standardized delivery contracts: define consistent output artifacts per mode and require SHIP closeout documentation written in Chinese by default.
  • Autonomous BUILD goal execution: synthesize an implementation package queue from ready evidence and execute bounded local quality gates (code review, test verification, and security review when needed).

Quick Start

Ask the agent to run /ideate with your goal and constraints, then stop before any production-code edits.

Frequently Asked Questions about aili-delivery-flow

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

FAQPage Schema
How does lifecycle orchestration enforce release readiness during build automation?▼

Lifecycle orchestration enforces release readiness by applying hard gates across IDEATE, DEFINE, BUILD, and SHIP modes, stopping execution when mandatory approvals, artifacts, or fresh verification evidence are missing.

How do I start spec authoring and test planning from an initial idea?▼

To start spec authoring and test planning, trigger the IDEATE mode with your goal and constraints, which shapes the idea and routes it into the DEFINE stage for structured test planning without production-code edits.

Can I use backend routing with custom files while preserving evidence gates?▼

Yes, backend routing selects an appropriate adapter like OpenSpec, plan-based, or custom files, while consistently preserving lifecycle evidence gates and verification constraints throughout the process.

What happens when verification evidence is missing or unverified during build automation?▼

When verification evidence is missing, the lifecycle blocks progress and labels states as Unverified, requiring explicit acceptance or waivers before autonomous BUILD goal execution can resume.

Does autonomous build execution support local quality gates for code review?▼

Yes, autonomous build execution synthesizes an implementation package queue from ready evidence and executes bounded local quality gates including code review, test verification, and security review.

Why does release closeout require specific documentation formats?▼

Release closeout requires specific documentation to standardize delivery contracts per mode, ensuring consistent artifact outputs and mandating SHIP closeout documentation written in Chinese by default.

Related Skills

Explore More Software Engineering Skills→
misty-stepmisty-step
2

shape

Shape vague backlog items into a context packet with goals and constraints.

Official
Advanced
cc01cccc01cc
4

npm-prepublish-check

Automate npm pre-publish quality gates for release readiness.

Community
Advanced
vladm3105vladm3105
16

doc-spec

Convert completed SDD artifacts into machine-readable SPEC YAML documents.

Community
Advanced
SJTU-IPADSSJTU-IPADS
7

coding-lead

Route coding tasks by complexity with ACP and direct fallback.

Official
Advanced