evo-quick-dev-new-preview

To generate production-ready code artifacts, provide a clear change request or user story. The skill translates intents into tech-specs and PR-ready code that aligns with existing architecture, patterns, and coding standards.

Yes, you can automate refactoring and feature development by supplying intent. The skill applies these changes across a codebase, producing artifacts that conform to project conventions with minimal risk.

A tech-spec in automated code generation is a foundational document outlining the implementation approach. This skill produces tech-specs alongside PR-ready artifacts to ensure code changes align with architecture before implementation.

Yes, this code generation approach works for fixing and tweaking existing code. It transforms specific intents into targeted, production-ready artifacts that match your current coding standards and patterns.

The best way to ensure generated code matches your architecture is to use a dev-automation skill that explicitly aligns outputs with existing patterns. It produces artifacts conforming to project conventions to reduce drift.

You do not need a full user story, but you must provide a clear change request or intent. The skill processes this input to generate the corresponding tech-spec and production-ready code artifacts.