This is much easier when packets follow a standard format, so I'd like to here argue for a QB Standard Packet Markup (or whatever you want to call it). The following proposal is largely inspired by ACF's format, and is designed to be the best mix of human readable, machine readable, pretty, and easy to generate. It's really only concerned with the larger format, though I'll likely come back later and make proposals for things as specific as powermarks, prompts, and pronunciation guides.
Without further ado, here's a general "visual" guide to what I'm looking for:
[Any intro fluff you like, such as round #, tournament name, authors, etc.]
1. Question text, in a single paragraph block if using Word or similar formats, or a single line if using simple text formats.
ANSWER: the answer goes here
2. We number each question using the format "#. ", where there's the number of the question, a period, then whitespace, before the question begins anew.
ANSWER: another answer
3. Every answer must appear in a separate line and be prefaced with "ANSWER: ", including the colon and the whitespace. The usage of all caps is preferred, but optional.
ANSWER: yet another answer
21. Tiebreaker questions also follow this format, regardless of whether a header is applied beforehand to separate the tiebreakers (such as a line reading "Tiebreakers" or splitting the tiebreaker questions to a new page.
ANSWER: tiebreaker answer
1. Whether or not the bonuses appear on a new page, a "BONUSES" header must be used to separate the bonuses. For 10 points each:
 This allows easy discovery of the bonuses even if the number of tossups varies from tournament to tournament.
ANSWER: a bonus part answer
 Note that the leadin again follows the "#. " format, but resets at 1 for the bonuses (though this isn't required).
ANSWER: another bonus part answer
 Bonus parts themselves should begin with the " " format, which uses square brackets and a point value. Use of whitespace and a consistent 10 points bonus part system is preferred, but optional.
ANSWER: a third bonus part answer
2. Note that the "For 10 points each: " suffix for leadins is not actually required, and that writers are free to choose whatever they like. For 10 points each:
 This is since, at all times, the point value should actually be read from the square bracket format instead.
ANSWER: bonus part answer
 Also note that we continue with the single line "ANSWER: " format from tossups.
ANSWER: more bonuses
 And that's about it!
21. Some last comments, for 10 points each:
 Author and category tags should a[*]ppear either at the end of the answerline, or in a new line after the answerline. The former is preferred, and the usage of such tags itself is preferred, but optional.
ANSWER: For example, you can do this, but putting the tags after the question (as below) is preferred: <Raynor><Literature>
 No content should appear in the packet after all questions.
 And that really is about it, now!
To tl;dr the important stuff:
- Preface tossup texts and bonus leadins with "#. "
- Preface tossup and bonus answers with "ANSWER: "
- Preface bonus parts with " "
- Use a "BONUSES" header to note the beginning of bonuses.
As you can tell, this is pretty close, if not identical, to what ACF and most housewrites use already, with some rare exceptions. I'd like to keep it that way, but also formalize the format, especially for new writers wondering what a packet should look like.
To repeat myself, I'd also like to come back to superpowers, powers, pronunciation guides, and prompts in the future, but I'll save that for the v2 of this post.
Anyways: thoughts? Use cases I'm obviously missing? Things that are just a hassle for writers?