vt-su-hc-content-propose

Create structured content proposals from qualified inbox items. Generates target section, proposed titles in all supported languages, article outline, and key points to cover. Enriches items in content/01-proposals/ with actionable structure for content creation.

Plugin: support
Category: Other
Command: /vt-su-hc-content-propose

---

Help Center Content Propose

Take a qualified inbox item and create a structured content proposal with titles, outline, and key points — ready for /vt-su-hc-content-create to generate the actual articles.

Invocation

/vt-su-hc-content-propose                          # Interactive — pick from proposals
/vt-su-hc-content-propose customer-feedback.md     # Specific file
/vt-su-hc-content-propose --all                    # Process all qualified items

Process

Step 1: Load Qualified Item

1. Read file from content/01-proposals/
2. Verify status: qualified in frontmatter
3. Load existing qualification metadata (target_category, source_language, estimated_articles)
4. If no file specified: list all qualified items and let user pick via AskUserQuestion

Step 2: Analyze and Structure

1. Read the source content thoroughly
2. Identify individual articles that can be extracted (one topic = one article)
3. For each identified article, generate:
4. Slug — kebab-case filename (based on German title, ASCII-safe)
5. Titles in all active locales:
   • de: German title
   • en: English title
   • nl: Dutch title (if content allows, otherwise mark as "needs translation")
   • ro: Romanian title (if content allows, otherwise mark as "needs translation")
6. Target section — which Zendesk section this belongs to (with section slug)
7. Outline — 3-5 bullet points covering what the article should address
8. Key points — specific facts, steps, or details that MUST be included
9. Source quotes — relevant text from the original that should be preserved

Step 3: Present Proposal

Display the structured proposal for user review:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Content Proposal: [source file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Articles to create: N

1. [slug].md
   DE: "German Title"
   EN: "English Title"
   Section: [section-slug]
   Outline:
     - Point 1
     - Point 2
     - Point 3

2. [slug].md
   ...

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Use AskUserQuestion: - Approve proposal — write proposal file, update status - Modify — user adjusts titles, sections, or outline - Split differently — user wants different article boundaries - Reject — mark as rejected

Step 4: Write Proposal

1. Update the file in content/01-proposals/ with enriched frontmatter:

   ---
   status: proposed
   proposed_at: "YYYY-MM-DD"
   source_file: "original-filename.md"
   target_category: faq
   articles:
     - slug: "wie-registriere-ich-mich"
       section: "registrierung-unternehmenseinrichtung"
       titles:
         de: "Wie registriere ich mich bei VisiMatch?"
         en: "How do I register on VisiMatch?"
         nl: null
         ro: null
       outline:
         - Registration steps
         - Email verification
         - Company setup
       key_points:
         - Each person should have their own account
         - Shared accounts are discouraged
     - slug: "passwort-zuruecksetzen"
       section: "konto-einstellungen"
       titles:
         de: "Wie setze ich mein Passwort zurück?"
         en: "How do I reset my password?"
       outline:
         - Reset via email link
         - What to do if email doesn't arrive
   ---
   

2. Keep the original content in the body for reference

Section Mapping

Read available sections dynamically from sync/mapping.yaml in the Help Center repo. Do NOT hardcode section slugs or IDs — mapping.yaml is the single source of truth.

Process: 1. Read sync/mapping.yaml 2. Parse the categories: and sections: entries to get available section slugs and Zendesk IDs 3. Present available sections to the user when assigning articles to sections 4. If sync/mapping.yaml does not exist or sections: is empty: warn the user and ask them to populate it first (section IDs come from Zendesk Admin)

Integration

• Input: Qualified items from /vt-su-hc-inbox-qualify in content/01-proposals/
• Output: Enriched proposals with article structure, titles, and outlines
• Next skill: /vt-su-hc-content-create generates Markdown articles from proposals