I have always been of the opinion that the majority of these systems are not concrete, and you are able to adapt them to your needs.
The Pomodoro technique in my opinion is designed to help you focus, with the concept that short bursts help you concentrate on your tasks. This is done by allowing you to break tasks into smaller components and less time, thus allowing you to break the cycle of long tedious tasks.
However as I mentioned in my opinion this should not be concrete, if you start off with a task which initially you set for 20/25 minutes, and you can focus more, then you should keep going. Remember it is all about getting you to focus and when you do keep the focus if you can. Give it a go and see how it works out, increase you task interval time.
2so, assuming that getting into "flow" is in general a good thing and beneficial to the work and its quality, I would conclude from your answer that it is better to skip a break, as long as you are focused and ready to continue working. I've done that myself when using Pomodoro technique, as I usually need it (as described in Jay's answer) to stay focused in face of distractions, and I generally found it positive so stay working longer (and then after the prolonged work time take a longer break as a reward) – MostlyHarmless – 2013-09-08T21:09:14.653
@Martin: Yes, that's correct. But it's a violation of the Pomodoro rules. (That's why I'm quite skeptical about Pomodoro.) – Gruber – 2013-09-09T05:43:15.557
@Gruber, I agree with Martin. If you are deeply engaged into some task and you are still focused, it's better to stay on task. I do this while designing software. When I am completely engaged into a system, visualizing the design and flow, I do not take break until I feel exhausted. But for other general tasks, like checking emails, creating or reading documents etc., I take breaks after 25 minutes. – matrix – 2013-09-13T18:33:21.743