evo-quick-dev

Implement quick technical specifications by following the evo quick-flow workflow.

Updated Apr 6, 2026

Search Tags:#automation #workflow #coding #software-engineering #rapid-implementation #quick-spec #evo

Ready to run

npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-quick-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evo-quick-dev
Source: https://github.com/DavidsonGomes/claude_cowork_workspace/tree/main/.claude/skills/evo-quick-dev
Command: npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-quick-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly translate a user-provided quick tech spec into concrete development steps by loading and following a predefined evo quick-flow workflow.

Core Features & Use Cases

Deterministic workflow execution: Loads the evo-quick-flow and follows its steps to implement the spec.
Small-change focus: Optimizes for rapid, low-risk feature additions.
Auditable process: Generates traceable changes aligned with project conventions.

Quick Start

Load the user's quick tech spec and trigger evo-quick-dev to begin implementing the requested change.

Frequently Asked Questions about evo-quick-dev

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

FAQPage Schema

How do I implement quick technical specifications deterministically?▼

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.

Can I use deterministic workflow execution for small feature changes?▼

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.

What is the best way to translate a quick tech spec into concrete development steps?▼

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.

Do I need a specific workflow file to automate rapid software implementation?▼

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.

Does the evo quick-flow workflow support auditable process generation?▼

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.

When should I not use a deterministic workflow for coding tasks?▼

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.