How To Write Comptia Linux Plus Items From Pasted Objectives
Linux+ items fail when they replay remembered stems. Paste objectives. Write one new item.
The matching generator is the CompTIA Linux+ Item Writer from Pasted Objectives (No Dump) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Quote the objective ID from Inputs
Write one multiple-choice item (stem, 4 options, one key, why-wrong) from pasted objectives. Do not invent exam codes if UNKNOWN. Not Network+, not Security+, not a brain dump. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Pasted objective text: [Objective]
Exam code I may print (or UNKNOWN): [Code]
Domain/label I allow (or UNKNOWN): [Domain]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Tools/commands I may mention (quote only from Objective): [Tools]
Cognitive level I allow (or UNKNOWN): [Level]
Banner I require: [Banner]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Write one stem and four options
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Objective nouns, Code, Domain, Tools, Level, Lang. Forbidden: remembered stems, inventing exam codes.
- Banner: print Banner.
- Stem: one question aligned to Objective only.
- Options A-D: one key + three distractors plausible from Objective vocabulary. Mark KEY.
- Why-wrong: one line per distractor. No invented man-page behavior beyond Objective/Tools.
- Mapping: Domain and Code or UNKNOWN.
- Refuse: Network+ items, Security+ items, brain-dump recall, inventing XK0-xxx if Code UNKNOWN.
- Compliance pass: quote Banned and Never. Gaps list of five. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Rationale for the key and each distractor
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- One Linux+ style item from Objective only. Not Network+/Security+ and not a dump.
- Never invent exam codes when UNKNOWN.
- Keep Banner visible.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse remembered exam dumps
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (comptia linux plus item writer, linux plus stem distractors, no exam dump) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.