#016 — Specification as the New Source Code

Date: August 28, 2026 | 19:00 London / 21:00 Kyiv
Format: Guest talk · technical deep-dive · ~70–80 minutes
Guest: Oleksandr Blazheiko
YouTube: https://youtube.com/live/dy79Bdktwxo
Participants
Oleksandr Blazheiko — Software Development Engineer · Fullstack
Ukraine
LinkedIn · itvibe.party
What we'll cover
An AI agent writes code faster than any team — but anything you didn't specify, it fills in with its best guess. Oleksandr Blazheiko walks through the set of documents you hand an agent so the result is a working system, not a nice-looking prototype with the wrong logic.
Topics
- Why an agent guesses instead of asking — and what that costs you
- How the team's way of working shifts once an agent writes part of the code
- Five layers of context: Brief → Functional → Non-Functional → Acceptance Criteria → Contracts
- Acceptance criteria (Given/When/Then) — a document that is task, test, and sign-off at once
- AGENTS.md / CLAUDE.md — the rules file an agent actually reads
- How to verify an agent got it right, instead of just trusting "tests passed"
- Seven common mistakes when handing work to an agent
- A Definition of Ready checklist before launching an agent
- How team roles shift — from a classic pipeline to a solo developer running agents
Key takeaways
Added after the stream.
Timecodes
Added after the stream.
Resources
- Slides — Specification as the New Source Code (Oleksandr Blazheiko)
- Gherkin (Given/When/Then) — official Cucumber reference
- OpenAPI Specification
- RFC 2119 — Key words for use in RFCs
- AGENTS.md — open format for agent instruction files
- itvibe.party — Oleksandr Blazheiko's project
- LinkedIn page
- Telegram community
- Discord server

