How to add features to an existing app
Follow these steps in Evonx to new functionality merged into a live codebase with reviewable diffs.
Step-by-step
Write a narrow spec
User story, acceptance criteria, and non-goals for the change.
Point Evonx at the repo
Confirm branch strategy and coding conventions in the prompt.
Request incremental PRs
Prefer smaller changesets that pass CI over massive rewrites.
Review security touchpoints
Auth, payments, and PII paths need explicit human review.
Update docs and tests
Ask for tests where the project already uses them; update README if behavior changes.
Deploy with your pipeline
Use existing staging/production processes—Evonx does not replace DevOps.
Outcome
New functionality merged into a live codebase with reviewable diffs.
Related resources
FAQ
How big should the first feature thread be?
Small enough to preview and review in one PR—one user-visible outcome with clear acceptance checks.
What if requirements are unclear?
Describe observed behavior and constraints first; use preview as the shared artifact for stakeholders.
Can non-engineers participate?
They can specify outcomes and review previews; engineers still own merge and production safeguards.
Build production software with Evonx
Start from a template or connect an existing repository. Evonx helps you ship real applications with preview, evolution threads, and pull-request delivery—not disposable demos.