aili-delivery-flow

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.