Design near-complete templates for recurring outputs — section headings, formatting, and boilerplate pre-filled, requiring only variable content insertion

Why This Is a Rule

Recurring operational outputs (weekly status reports, bug reports, meeting minutes, standup updates) share a predictable structure that's the same every time. The section headings don't change, the formatting is consistent, and much of the text is boilerplate: "This week's progress:", "Blockers:", "Next steps:", "Attendees:". Recreating this structure from scratch each time is wasted effort — cognitive resources spent on formatting and organization rather than on the variable content that makes each instance unique.

A near-complete template pre-fills everything that's constant: structure, headings, formatting, boilerplate text, and even placeholder prompts ("Insert this week's metrics here"). The producer's job reduces from "create a report" (30 minutes of structure + content) to "fill in the blanks" (10 minutes of content only). The 20-minute savings per instance compounds across 50 instances per year into 16+ hours of recovered production time.

The "nearly complete" qualifier is deliberate: the template should be so complete that the producer needs to add only the variable content — the data, decisions, and observations that are unique to this instance. If the producer still needs to make structural decisions (where to put this section, how to format this data), the template isn't complete enough.

When This Fires

• When creating any output type for the second time — that's when the template should be extracted
• When recurring outputs take longer than they should because of repeated structural work
• When output quality varies across instances because the structure is recreated each time
• Complements Extract templates from your 3 best past examples by finding common structure — don't design templates from theory (extract templates from best examples) with the design specification for template completeness

Common Failure Mode

Skeleton templates: templates with section headings but no formatting, no boilerplate, and no prompts. "Status Report Template: [Title]. Progress. Blockers. Next Steps." This saves 2 minutes of heading creation but doesn't address the 15 minutes of formatting, boilerplate writing, and structural decisions that the producer still faces each time.

The Protocol

(1) After producing a recurring output for the third time, extract a template. (2) Include everything that was identical across all three instances: section headings, formatting, boilerplate text, standard recipients, standard intro/outro paragraphs. (3) Mark variable sections with clear prompts: "[Insert this week's top 3 accomplishments]" "[Insert current blockers with expected resolution dates]" "[Insert next week's priorities]." (4) Test: can someone produce the next instance by only typing into the bracketed prompts? If they need to make any structural decisions, the template needs more pre-filling. (5) Version the template: when the output format evolves (new section added, old section dropped), update the template immediately rather than letting instances diverge from the template.