Kituwa IT · Field guide
A reusable prompt that produces useful drafts
Use a six-block template. Goal: what should the draft accomplish? Practical checks and official references.
Use a six-block template.
This guide expands the Facebook post into a practical workflow for beginners, home-lab users, and small-business owners who want to understand the trade-offs before changing a working system.
What this guide covers
- A reusable prompt that produces useful drafts
- Six blocks, clearer instructions.
- Goal — What should it do?
- Audience — Who reads it?
- Sources — What must it use?
- Constraints — Length, tone, avoid
Why it matters
The goal is not to memorize a product name or copy a command blindly. It is to understand what the change affects, verify it against an official reference, test it on spare hardware or a virtual machine when possible, and keep a rollback path.
A practical walkthrough
Check the assumptions
Goal: what should the draft accomplish? Audience: who reads it, and what do they know? Source material: which facts, documents, or examples must be used? Constraints: length, tone, format, things to avoid. Output format: headings, bullets, table, or plain text. Verification: ask the model to list assumptions and flag anything it could not verify.
Step 2: what to check
Example: a fictional service FAQ. Before: “Write an FAQ.” After: “Write a 6-question FAQ for a small business owner comparing two support plans. Use only the attached plan table. Use plain language, 80-120 words per answer, and flag any missing detail.”
Step 3: what to check
The second prompt is not magic; it is clearer about the job. A reusable prompt should include an example of a good answer and a known bad answer. Store it with the source material. Save the template and reuse it; do not retype it every time.
Your turn
Which block do you usually forget?
What to verify
- Use the official documentation for the exact version you run.
- Test on a spare device or virtual machine before changing a working system.
- Keep a backup and a rollback path.
- Record what changed and how you verified it.
Common mistakes
- Trusting a confident answer without a check.
- Skipping a repeatable test set or factual review.
- Sending private data to an endpoint you have not verified.
Quick checklist
- ☐ Six blocks, clearer instructions.
- ☐ Goal — What should it do?
- ☐ Audience — Who reads it?
- ☐ Sources — What must it use?
- ☐ Constraints — Length, tone, avoid
- ☐ Format — Headings, bullets, table
FAQ
What is the first step?
Use a six-block template.
What should I avoid?
Trusting a confident answer without a check.
Where can I verify the current details?
Use the official references below; versions and interfaces change.
References
Related guides
- RAG vs fine-tuning vs better prompting
- The AI task you should keep reviewing
- AI skills are not magic slash commands
Need help?
If you want a second opinion on the setup or the rollback plan, Kituwa can review it with you. Start with the checklist above; it makes the conversation more useful.