Created DeAndre Tutor agent and /deandre-tutor command - #20
Created DeAndre Tutor agent and /deandre-tutor command#20ReasonedClub55 wants to merge 2 commits into
Conversation
eric-sabe
left a comment
There was a problem hiding this comment.
Thanks for this, @ReasonedClub55 — it's a genuinely well-crafted persona, and it fills a real gap. engsys's audience includes people learning from multi-agent sessions, and nothing in the current roster teaches: gary critiques, the interactive-explainer skill builds visual artifacts, but nobody translates a session into understanding. DeAndre does, and the craft shows — the clear role boundaries ("you don't code, you don't decide, you don't manage — you explain"), the disciplined output structure, the concrete worked examples in the command spec, and model: sonnet is exactly the right tier for this work. We'd like to take it.
Two structural changes needed before merge, both about where it lives rather than what it is:
-
Move
deandre.mdfromcore/agents/tooptional-agents/. Core agents are the always-installed engineering loop; nice-to-have personas live inoptional-agents/(see sandy, jos, steve) and users opt in viaagents.extra: [deandre]in their config. DeAndre is squarely in that second category — as submitted, every default install would ship him. -
Fold the command into the persona and drop
core/commands/deandre-tutor.md. Commands undercore/commands/install for everyone (commands: all), so once the agent is optional,/deandre-tutorwould install with no agent behind it — which is why the other optional personas ship no commands. The good news: your command file is essentially DeAndre's output spec, and it's the strongest part of the PR. Move the "Output Structure" sections (Session Goal → Team & Roles → What Happened → Key Concepts → Why It Mattered → Tradeoffs → Next Steps, with the examples) into the persona under something like### Output format (teaching summary). His frontmatterdescriptionalready triggers use when someone asks for a session explanation — no slash command needed.
Two tiny nits while you're in there:
- A 45-year-old retired professor with "four decades explaining hard things" started teaching at age five 🙂 — tighten one or the other (we'd vote for keeping the four decades and losing the age).
deandre.mdis missing a trailing newline.
If you'd rather not do the restructure, say the word and we'll fold it in on merge with you credited — but we wanted to offer you first crack, since the persona's voice is yours. Either way, this is a welcome contribution and we'd be glad to see more from you.
…d into persona - Move deandre.md from core/agents/ to optional-agents/, since he's an opt-in persona rather than part of the always-installed core loop - Drop core/commands/deandre-tutor.md and fold its output-structure spec into deandre.md under a new "Output format (teaching summary)" section, since optional personas don't ship their own core commands - List deandre alongside sandy/jos/steve in engsys.config.example.yaml - Drop the "45-year-old" detail (contradicted "four decades" of teaching) - Add missing trailing newline to deandre.md
|
Thanks for the thorough review! I've pushed a commit addressing all of it:
Let me know if anything else needs adjusting! |
DeAndre — The Teaching Translator
DeAndre is a retired university professor who translates complex AI engineering sessions into clear, educational narratives. When a session involves multiple agents, intricate decisions, and technical tradeoffs, DeAndre digests what happened and explains it so a careful undergraduate can understand—without losing precision or substance.
What he does:
Produces a teaching summary of the current session. Organize your work as: Session Goal → Team Roles → What Happened (major phases) → Key Concepts → Why It Mattered → Tradeoffs & Constraints → Next Steps. Output reads like a helpful lecture, not a log.
When to use him:
You need a clear explanation of what happened in a multi-agent session
You want to understand the why behind decisions, not just the what
You're learning and want concepts explained without developer jargon overhead
You need a reference to revisit and build understanding from