01Define the prompt template selection behind prompt lists
For Prompt Lists, state the subject, environment, action objective, emotional beat, and end condition in plain production language. These invariants keep general prompt planning variants comparable instead of producing unrelated ideas. Treat a template, pack, gallery, card, database, or library as a reusable decision scaffold. Label required fields and optional fields, replace examples with authorized project details, and remove assumptions about models, identities, products, formats, or outcomes before use. Write the decision owner and intended handoff beside the brief so a search phrase cannot be mistaken for a verified product capability or an instruction that has already been executed. For a controlled test, preserve the handoff draft, and ask the rights reviewer to record human approval before the rights check.
02Apply the general prompt planning structure
Turn the phrase into a production brief with a medium, subject, action, setting, composition, ordered beats, constraints, and a reviewable end state. Separate the durable creative direction from syntax that belongs to a particular interface. This makes the prompt useful even when tools, model names, or accepted parameters change. For “prompt lists”, keep a visible distinction between required content, optional treatment, exclusions, and facts that need evidence. That structure gives controlled variants a stable baseline and lets a reviewer identify which instruction caused a material change. For a controlled test, preserve the delivery checklist, and ask the delivery owner to record failure conditions before the workflow transfer.
03Prepare authorized inputs for general creative direction
This query calls for the intended medium, audience, purpose, authorized sources, subject, action, context, constraints, reviewer, and delivery condition. Turn broad or ambiguous words into observable choices. Define one outcome, order the important decisions, remove contradictions, and keep optional style language separate from required content. Record the source, permission, intended audience, protected details, and reviewer before testing language. The goal is a traceable creative proposal, not an assumption that a named platform, model, or workspace will perform the requested action. For a controlled test, preserve the decision history, and ask the release approver to record revision intent before the source comparison.
04Build controlled variants and observable acceptance checks
For this owner, the first review pass should make lists observable rather than merely decorative. Change one meaningful dimension per version and label the hypothesis, invariant details, expected difference, and rejection condition. A template is ready when its placeholders are fully resolved, its structure matches the production job, and a reviewer can distinguish source facts from creative proposals. Keep failed variants in the decision record so the final wording is explainable rather than selected by impression alone. At the next gate, preserve the claim inventory, and ask the accessibility reviewer to record disclosure clarity before the production checkpoint.
05Review authorization, safety, and changing product facts
Treat unclear product, entity, and platform references as questions. Do not invent capabilities, facts, identities, access terms, or production results to fill a gap in the query. Use only authorized source material, preserve attribution and provenance, avoid deceptive identity or factual claims, and verify any changing product or platform statement in current first-party documentation. Treat every named model, competitor, access term, platform rule, identity use, commercial claim, and output specification as a dated evidence question. If authorization or first-party support is missing, keep the language editorial, stop the handoff, and record the unresolved gap instead of inventing a workaround. Before moving on, preserve the claim inventory, and ask the workflow owner to record evidence freshness before the editorial approval.
06Approve a reversible prompt handoff
Read the prompt once for intent, once for visual or temporal coherence, and once for rights and factual risk. Remove decorative terms that do not change an observable decision, then test controlled variants rather than rewriting every instruction at the same time. Before approving “prompt lists”, check purpose, source rights, identity consent, factual support, continuity, disclosure, destination requirements, and the named review owner. Preserve the original brief and version notes. This handoff supplies authored guidance only and neither runs generation nor guarantees access, quality, speed, licensing, publishing, downloads, or outcomes. Before moving on, preserve the authorization record, and ask the factual editor to record control availability before the editorial approval.
