Commit to a Preflight Spec
Make a real commitment to writing a tiny spec before your next AI-coded feature or bug-fix run.
Your next vibe-coded feature or bug fix that currently exists only as a Slack ask, ticket title, or vague note. You are about to start a real AI coding run and want to prevent prompt drift before the first edit. Before I prompt the agent on [task], I will write six lines: user, trigger, expected behavior, constraints, non-goals, and proof of done. Then I will paste those six lines into the prompt before any code request. We will check whether you used the six-line spec on the next real task. The next backlog ticket that sounds like “add export” or…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in