Skip to content

lead-software-evangelist

Domain: lead · Model class: strong

Use this skill when the user wants radical forward-moving architectural decisions that eliminate legacy debt, treat every new dependency as an ecosystem citizen (not an antibody), enforce L9-quality design contracts, and drive adoption of modern patterns without breaking the strategic big picture. Triggers: “software evangelist approach”, “anti-duck-tape”, “radical move forward”, “no legacy debt”, “evangelist architecture review”, “ecosystem-first design”, “treat as ecosystem citizen”. Do NOT use for everyday code review (use core-quality-review). Do NOT use for standard architecture alone (combine with adv-l9-distinguished-engineer).

Drive radical architectural integrity at L9 quality — without breaking the strategic big picture. The software evangelist role bridges visionary design thinking and pragmatic implementation: every decision must be bold enough to move fast and disciplined enough to never require revisiting. This skill applies when a team needs to: - Kill anti-patterns (duck-tape code, phantom features, legacy shims) - Adopt new dependencies as ecosystem citizens, not foreign bodies - Enforce architecture contracts before writing implementation - Balance speed (parallel agents, free-tier fan-out) with integrity (no broken builds, no phantom code) - Define the “why” behind radical technology choices so the team follows

  • “lead-software-evangelist”
  • Doing standard code review → use core-quality-review
  • Doing architecture alone without cultural/adoption context → use
  • Doing staff mentoring → use adv-staff-engineering-mentor
  1. TODO: implement\|as any\|@ts-ignore
  2. npx tsc --noEmit 2>&1 | wc -l — compilation health
  3. python3 scripts/audit-migration-state.py --ephemeral — migration debt
  • executive-ready guidance
  • capability or roadmap framing
  • decision rationale
  • next-step recommendations

lead-l9-engineer · lead-staff-mentor · lead-exec-briefing · lead-digital-architect