# Build workflow

> Guides to the Vibely build workflow: how to direct the agent, plan before it writes code, keep the code in your own GitHub repo, and spend fewer turns.

Canonical: https://vibely.sh/guides/category/workflow
Last updated: 2026-09-27

How to direct the agent, keep the code in your own repo, and spend fewer turns doing it.

3 guides

- [How to use plan mode](https://vibely.sh/guides/how-to-use-plan-mode) - A read-only turn that reads your code and answers before anything is written. One plan turn routinely saves three wrong builds.
- [How to sync your project to GitHub](https://vibely.sh/guides/how-to-sync-your-project-to-github) - Two-way sync with a repo you own: every build is a commit, every push flows back. Plus what "diverged" means and why it quietly stops your branch updating.
- [How to create an app: a step-by-step guide](https://vibely.sh/guides/how-to-create-an-app) - Seven steps from an idea to an app people can use: pick the problem, choose web or mobile, build with code, no-code or AI, then test and publish it.

## Related

- [Mobile apps](https://vibely.sh/guides/category/mobile)
- [Connect a service](https://vibely.sh/guides/category/integrations)
- [Launch and publish](https://vibely.sh/guides/category/launch)
- [Troubleshooting](https://vibely.sh/guides/category/troubleshooting)
- [Account and billing](https://vibely.sh/guides/category/account)
