A task packet answers seven questions
Define the task before selecting any processing method:
- What exact outcome should this work produce?
- Which sources may support the result?
- Which material sits outside the task?
- What format must the result use?
- Which actions may the process take?
- What should cause the work to stop?
- How will a separate review judge the artifact?
One packet owns one job. If a missing decision would change the path, record the question instead of burying an assumption inside a prompt.
See the boundary in a synthetic brief
The fixed workshop note names independent consultants, a two-hour planning session, and a requirement to use confirmed details only.
The task requests one concise Markdown content brief. It includes the confirmed audience, offer, and constraint. It excludes an unconfirmed schedule and price. Work stops when a reviewed corrected brief and checkpoint exist.
That stopping condition matters. A missing fact becomes an unresolved question, not a confident sentence.
Use the packet to control review and correction
The draft includes “Saturday sessions are available.” The task packet contains no schedule source. Separate review identifies the mismatch and requests removal.
The corrected brief preserves the audience, two-hour offer, and confirmed-detail constraint. Its export includes the packet, source note, first brief, finding, corrected brief, and checkpoint with schedule and price unknown.
The demonstration shows traceability within fabricated material. It cannot prove subject-matter accuracy or model performance.
Choose this method when the work can drift
A task packet fits work with several sources, multiple steps, a durable output, or consequences beyond the current chat. A short exploratory question may need only a direct prompt when no file, account, decision, or external action changes.