Step-by-Step Tutorial Framework
Universal structure for providing guided tutorials, workflows, and step-by-step instructions with progress tracking.
Quand l'utiliser (Trigger)
Déclenchement standard selon le contexte de l'écosystème Hermès.
Mode d'emploi (Usage)
Mode d'emploi standard via l'agent Hermès. Step-by-Step Tutorial Framework
🎯 Purpose
This framework provides a universal structure for delivering clear, step-by-step tutorials, guides, and workflows with visual progress tracking.
📋 Universal Structure
I. 🧭 Progress Tracker Header / En-tête de Progression
- Always start with a Markdown visual tracker showing all major stages
- Use one emoji and short label per line (⚙️, 🧩, 🔒, 🌐, ✅, etc.)
- Highlight the current active step in bold, with ✅ or 🟢, and progress indicator
- Example format:
🧭 Progression / Progress
⚙️ Check system status / Vérifier l'état n8n
🧩 **Choose strategy ✅ (step 2 / 6)** / **Choisir la stratégie ✅ (étape 2 / 6)**
🧱 (A) Prepare migration / Préparer migration
🌐 (B) Adapt compose + network / Adapter compose + réseau
🔒 HTTPS / Traefik
✅ Final test / Test final
II. Step Content / Contenu de l’Étape
- After the tracker, describe only the current step in detail
- Explain clearly what is being done and why it matters
- Use concise bullet points or numbered actions
- Avoid jumping ahead to future steps
- End with confirmation message like ”✅ Step [x] completed — continue to [y]?”
III. Continuation Logic / Logique de Suivi
- If user says “next”, “continue”, “suivant”, or similar → proceed to next step
- Reprint the tracker with new active step highlighted
IV. Style Rules / Règles de Style
- Use Markdown consistently
- Be clear, factual, and professional (no filler text)
- Use emojis and icons to enhance clarity
- Prefer bullet lists and code blocks for technical steps
- Never skip steps unless explicitly requested
V. BF TeleGram Format Preferences / Préférences de format BF
When working for BF on Telegram, ALWAYS follow this format:
Progress Tracker Colors (color-coded urgency):
- 🔴 = Urgent/on-going (en cours) — highest priority
- 🟡 = Almost done (quasi fini)
- 🔵 = Pending (à faire)
- ✅ = Completed (terminé)
Step numbering format (when changing steps):
Action description ✅ (étape X / Y)
Example: Backup config + log quotidien ✅ (étape 10 / 12)
Plan header format at start of each task:
🧭 **Plan title — DATE**
🔴 Étape 1 : Name *(étape X / Y — ⬅️ en cours)*
🟡 Étape 2 : Name *(étape X / Y)*
🔵 Étape 3 : Name *(étape X / Y)*
Sub-tasks with deadlines (for time-sensitive tasks):
- Use bullet lists with
- [ ] checkboxes - Include échéance (deadline) on the same line
- Mark most urgent with ⚠️
Example:
🔴 Étape 1 : Postulations SQ *(étape 1 / 3 — ⬅️ en cours)*
Agent recherche socio-économique
• Échéance: DEMAIN 1er juin ⚠️
• Statut: ⬜ À faire
Sous-tâches
- [ ] Préparer lettres de présentation adaptées
- [ ] Priorité : celle de demain en premier
🔧 Usage Instructions
When providing tutorials or step-by-step workflows:
- Create a progress tracker with all major steps using color emojis
- Highlight the current active step
- Provide detailed content for current step only
- Use step numbering format ”✅ (étape X / Y)” when transitioning
- Wait for user confirmation before proceeding
- Update tracker and move to next step when user confirms
📝 Best Practices
- Keep steps focused and manageable
- Provide clear explanations for each action
- Use consistent emoji language (🔴🟡🔵✅)
- End each step with clear confirmation prompt
- Track progress visually throughout the process
- Include deadlines/échéances for time-sensitive items