the-immortals
The Immortals
"Legends don't die. Their patterns outlive every codebase."
Orchestrate the five legendary developer personas — routing tasks to the right specialist(s) based on domain and complexity, then synthesizing their perspectives into a clear recommendation.
The Council
| Agent | Role | Domain | Emoji | Direct override |
|---|---|---|---|---|
fowler |
The Architect | Design patterns, refactoring, structure | 📐 | @fowler |
beck |
The Craftsman | TDD, XP, simplicity | 🔴 | @beck |
uncle-bob |
The Purist | Clean Code, SOLID, naming | 🧹 | @uncle-bob |
evans |
The Domain Whisperer | DDD, ubiquitous language, bounded contexts | 🗺️ | @evans |
linus |
The Dissenter | Performance, pragmatism, devil's advocate | ⚡ | @linus |
More from yldgio/vibe-grimoire
pre-mortem
>-
13create-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue, Azure DevOps work item, or local file. Use when the user wants to create or write a PRD, create a product requirements document, design a new feature, or capture requirements.
11setup-repo
>-
11prd-slice
Break a PRD into independently-deliverable work items (vertical slices / tracer bullets) and create them in Azure DevOps, GitHub Issues, or Jira. Use when a user wants to convert a PRD into implementation tickets, decompose a product spec into trackable slices, create work items from requirements, or break down a PRD for any issue tracker — even if they don't say "vertical slice" or "tracer bullet".
11plan-from-prd
Turn a PRD into a multi-phase, local Markdown implementation plan using tracer-bullet vertical slices, saved to ./plans/. Use when the user wants to create an implementation plan from a PRD, plan phases from a PRD, break a PRD into development phases, or mentions "tracer bullets" or "implementation phases". For creating tracker work items (GitHub Issues, Azure DevOps, Jira) use the prd-slice skill instead.
11tdd
>-
9