Write a work-anniversary post for [years] at [company]

This is the assembled prompt after inserting any variables you filled in. Placeholders that are not filled remain in [brackets]. You can optionally edit the prompt below without changing the variable inputs.

VALIDATE INPUTS:

- Missing / ambiguous items (explicitly noted): [company] (company name), [years] (numeric milestone), [platform] (e.g., LinkedIn, X), [audience] (e.g., colleagues, managers, clients), [tone] (e.g., warm-professional, celebratory, reflective), [length_words] (target word count), [call_to_action] (what to ask readers to do).
- Clarifying questions: none will be asked. Proceeding with explicit assumptions below.

ASSUMPTIONS (applied if placeholders are blank):

- If [platform] is not provided, default to "LinkedIn".
- If [audience] is not provided, default to "colleagues and professional network".
- If [tone] is not provided, default to "warm-professional".
- If [length_words] is not provided, default to 500 (±10%).
- If [call_to_action] is omitted, default to "invite readers to share a memory, congratulate, or ask a question".

PLAN — final prompt structure to be produced (frontmatter + body):

- Title
- Objective
- Role/Persona
- Context (delimited) — only the exact reference text allowed
- Task Instructions (ordered, explicit)
- Constraints and Rules (scope, forbidden items, length, tone)
- Output Format (exact structure to return)
- Evaluation Criteria (self-check list)
- Optional Reasoning instruction (public brief rationale allowed)
- Final Check (confirm placeholders and rules)
- Assumptions (as above)

ENFORCE PLACEHOLDERS:

- This prompt uses only these bracketed placeholders: [company], [years], [platform], [audience], [tone], [length_words], [call_to_action].
- Each bracketed placeholder above is listed in the frontmatter `placeholders` array exactly (case-sensitive match).

TITLE
Write a [length_words]-word work-anniversary post celebrating [years] at [company] for [platform]

OBJECTIVE
Produce a single, professional, and emotionally authentic work-anniversary post that: (1) clearly states the milestone ([years] at [company]); (2) reflects on impact and one concrete accomplishment; (3) expresses gratitude to people/teams; (4) ends with a clear [call_to_action]; and (5) matches the requested [tone] and [length_words] target (±10%).

ROLE/PERSONA
You are a Senior Content Strategist and LinkedIn Copywriter. Adopt a warm-professional, first-person voice that is concise, reflective, and network-appropriate. Tailor language for [audience].

CONTEXT (delimited)
"""
Celebrating work anniversary at a company for x years and writing a post about it.
"""

TASK INSTRUCTIONS

1. Read the Context block only for background. Do not add outside facts about [company] or unauthorized confidential details.
2. Produce one primary post that:

   - Begins with a 1–2 sentence hook that immediately mentions the milestone: "[years] at [company]".
   - Includes one concrete accomplishment or measurable impact (use non-confidential phrasing, e.g., "led a cross-functional team to launch [project]" — do NOT include confidential metrics or proprietary details).
   - Contains a short reflection (1–2 paragraphs) about lessons learned or how the role changed you.
   - Includes explicit gratitude: name roles/teams generically (e.g., "my team", "mentors", "customers") or use named individuals only if safe to do so.
   - Closes with the [call_to_action] (e.g., "I'd love to hear your advice", "Share a memory", "Connect if...").

3. Provide exactly two optional post elements after the main post:

   - A single-line alternative hook (one sentence) ready to A/B test.
   - A 30–60 word shortened caption variant for quick sharing.

4. Ensure all placeholders remain bracketed in the generated content only if the user left them unfilled; otherwise replace placeholders with provided values. (The generating system should substitute values before final public posting.)
5. Do not include any YAML, JSON, code fences, or markdown in the output — deliver plain text only.

CONSTRAINTS AND RULES

- Scope: Professional reflection only. Do not invent specific unreleased product details, internal KPIs, or confidential client names.
- Length: Target [length_words] words for the main post, allowed tolerance ±10%. The two optional elements should be exactly one sentence (hook) and 30–60 words (short caption).
- Tone/Style: Use the requested [tone]. Prefer active voice, first person singular ("I"), clear sentences, and no jargon that the [audience] wouldn't understand.
- Formatting: Plain text paragraphs separated by a single blank line.
- Forbidden: No salary figures, no confidential IP, no sensitive personal health/legal details, no defamatory content, no political campaigning.
- Compliance: Respect company social policies and confidentiality. If uncertain, default to generic role/team references.
- Reading Level: Professional audience (skilled professionals); avoid overly technical explanations.

OUTPUT FORMAT

- Medium: Plain text only (no markdown or code blocks).
- Structure (in this exact order):

  1. Hook line (1–2 sentences) — must mention "[years] at [company]".
  2. Blank line.
  3. Main body: 2–4 short paragraphs (reflection, accomplishment, gratitude).
  4. Blank line.
  5. Closing sentence with the [call_to_action].
  6. Blank line.
  7. "Alt hook:" then one alternative hook sentence (single line).
  8. "Short caption:" then the 30–60 word short variant on one line.

- Voice/Tense: First person, present/past as appropriate, active voice.

EVALUATION CRITERIA (self-check before returning)

- Does the main post explicitly state the milestone "[years] at [company]" in the hook? ✔
- Is the main post within [length_words] ±10% words? ✔
- Does it contain at least one concrete, non-confidential accomplishment/impact? ✔
- Is gratitude expressed to roles/teams or named people only if safe? ✔
- Does the closing contain the [call_to_action]? ✔
- Are there no forbidden items (salary, confidential KPIs, private data)? ✔
- Is the output plain text only and structured exactly per "Output Format"? ✔
- Are all bracketed placeholders used in the body listed in frontmatter `placeholders`? ✔

OPTIONAL REASONING

- Do NOT output chain-of-thought. If asked to explain choices, provide a brief public rationale (2–3 sentences) summarizing why the hook, example, and CTA were chosen.

FINAL CHECK (before returning the generated post)

1. Verify every bracketed placeholder in this prompt body matches an entry in frontmatter `placeholders`.
2. Confirm the Context block contains only the supplied reference line and nothing else.
3. Confirm no markdown/YAML/code fences are present in the output.
4. Run the Evaluation Criteria checklist and correct any failing items.

ASSUMPTIONS (applied when placeholders are not provided)

- Default [platform] = "LinkedIn".
- Default [audience] = "colleagues and professional network".
- Default [tone] = "warm-professional".
- Default [length_words] = 500 (accept ±10%).
- Default [call_to_action] = "Please share a memory or drop a congratulatory note."

USAGE NOTE

- Replace bracketed placeholders with actual values prior to public posting. If you leave placeholders in the final text, mark them clearly for the user to fill.