Run a guided study session for a CCNP ENCOR topic. Combines overview, deep dive, quick quiz, lab suggestion, and a summary card.
Step 1 — Identify the Topic
Parse the argument provided:
- If a number (e.g.,
19), find the matching folder: 19-STP-Algorithm/
- If a name (e.g.,
OSPF or STP), fuzzy-match against folder names
- If no argument, suggest the next topic the user should study: check which topic READMEs are still mostly empty (just the template) and suggest the lowest-numbered one
Read the topic's README.md before proceeding — reference it throughout the session.
Step 2 — Overview (2–3 minute read)
Present a structured overview:
- What it is — one plain-English sentence
- Why it matters for ENCOR — exam weight, typical question types, how often it appears
- Key terms — define 4–6 terms the user must know cold
- How it fits — how this topic connects to adjacent topics in the curriculum
Keep this section concise — it's the warm-up, not the deep dive.
Step 3 — Deep Dive
Walk through the topic interactively. Structure it around the README sections:
How It Works:
- Explain the mechanism step by step
- Use analogies where helpful (e.g., STP election = "the network votes for a root bridge like electing a team captain")
- Show a simple scenario/example
Configuration Commands:
- For each key command, explain: what it does, when to use it, what the output looks like
- Show a realistic config snippet in a code block
- Point out common syntax mistakes
Verification Commands:
- Show what to run after configuring
- Explain what healthy output looks like vs. signs of a problem
Exam Gotchas:
- Name 3–5 specific things the ENCOR exam loves to test on this topic
- Include common traps (e.g., "RSTP costs are the same as STP by default but negotiation is different")
After the deep dive, ask: "Any questions before we test your knowledge?"
Step 4 — Quick Quiz
Run 3 rapid-fire questions (no waiting between — present all 3, then review answers together):
- One definition/terminology question
- One "what happens when" scenario question
- One command syntax or verification question
Collect the user's 3 answers, then review them together:
- Mark each correct/wrong
- Give a brief explanation for any wrong answers
- Don't score formally — this is a quick check, not the full
/quiz
If the user got 2+ wrong, suggest: "Consider running /quiz [topic] for a deeper practice session."
Step 5 — Lab Suggestion
Suggest a specific, focused lab for this topic:
- Describe in 2–3 sentences what the lab would look like (topology, what to configure)
- Ask: "Want to generate the full lab guide? Run
/lab [topic] and I'll build it out completely."
If Eve-ng MCP is connected, mention: "Your Eve-ng server is connected — I can deploy it automatically."
Step 6 — Summary Card
End with a compact cheat sheet the user can copy into their README notes:
## [Topic Name] — Quick Reference
**What it does:** [one line]
**Key facts:**
- [fact 1]
- [fact 2]
- [fact 3]
**Must-know commands:**
- `[command]` — [what it does]
- `[command]` — [what it does]
**Exam traps:**
- [trap 1]
- [trap 2]
Tell the user: "Copy this into your topic's README.md under Exam Tips / Gotchas to build your notes as you study."
Notes
- Match the explanation depth to what the user signals — if they ask follow-up questions, go deeper
- Always tie concepts back to real ENCOR exam scenarios
- If the topic README is already well-filled, acknowledge it and build on what's there rather than repeating it
- If the user seems stuck or confused, slow down and use a different analogy