~aod-kickstart

To generate a consumer guide, you translate a project idea into a ready-to-use document by capturing the idea, selecting a stack, and generating 6-10 seed features. This process ensures consistent governance and rapid starter planning.

The best way to define seed features for the AOD lifecycle is to enforce a six-to-ten feature scope. The system arranges these features by Ordering Principles to ensure incremental value delivery across the generated guide.

Stack selection works by detecting an active pack or prompting you to pick a stack during the guide generation process. This ensures the final consumer guide aligns with your technical environment before outputting seed features.

Yes, you can execute deployment commands directly because the generated guide includes Quick Start commands and execution steps. These operational instructions seed features into /aod.discover to run the AOD lifecycle.

For idea intake and stakeholder alignment, you need to provide the idea description, target user, and key capabilities. This information seeds the guide generation process to produce a sequenced consumer document.

Yes, the guide generation process enforces a strict six-to-ten seed feature scope. It generates per-feature blocks arranged by Ordering Principles to maintain incremental value delivery within the AOD lifecycle.