evo-quick-dev

To implement quick technical specifications deterministically, load a user-provided quick tech spec and trigger the evo-quick-dev workflow. It processes small feature changes by loading and following predefined steps from the quick-dev workflow file.

Yes, you can use deterministic workflow execution for small feature changes. The evo-quick-dev workflow is specifically optimized for rapid, low-risk feature additions, applying a predefined set of steps to translate technical specs into concrete development actions.

The best way to translate a quick tech spec into concrete development steps is by loading the evo quick-flow workflow. It follows a structured, auditable process to generate traceable changes aligned with your project conventions.

Yes, you need the specific workflow file located at {project-root}/_evo/bmm/workflows/evo-quick-flow/quick-dev/workflow.md. The automation loads and follows this exact file to execute the rapid software implementation steps.

Yes, the evo quick-flow workflow supports auditable process generation. It ensures that translating a quick tech spec into development steps produces traceable changes that remain aligned with your project's established conventions.

You should not use a deterministic workflow for coding tasks when dealing with complex, large-scale features. This approach is specifically designed for small, rapid, and low-risk feature additions where predictable execution is required.