Vibe Coding Project Playbook
Purpose. Turn a plain-language idea into a tested, safer prototype with clear limits.
This guide gives team members a consistent starting point. Follow the current company policy and ask the named owner when a situation falls outside this guidance.
1. Define the job
Write the user problem, intended users, success condition, constraints and non-goals. Keep private credentials and sensitive data out of prompts and test fixtures.
2. Build a small slice
Ask the coding assistant for a small, understandable change. Review the proposed files and dependencies before accepting a large rewrite.
3. Inspect and test
Run the app, test the main path and likely failure cases, inspect permissions and data handling, and ask another person to review risky changes.
4. Release with limits
Deploy only to an approved environment with monitoring, rollback and a clear statement of prototype limits. Do not treat generated code as verified by default.
Questions and records
Ask your manager or the responsible process owner for help. Use approved company systems to record relevant decisions and follow-up actions. This fictional guide is for demonstration and must be reviewed before real use.