agents/skills/personas/SKILL.md
Switch to a specialized agent persona or invoke a persona directly. Use to delegate work to the right specialist.
npx skillsauth add drusifer/via personasInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
One-line summary: Switch to or invoke a specialist persona to delegate work to the right agent.
TLDR:
Use @<Persona> *<command> <args> for direct invocation, or describe the task via *chat for auto-routing to the best specialist.
Before switching: complete current action, post handoff to CHAT.md, save all three state files (context, current_task, next_steps).
Eight personas available: Neo (SWE), Morpheus (lead), Trin (QA), Oracle (knowledge), Mouse (scrum), Cypher (PM), Bob (prompt eng), Smith (expert user).
| Persona | Role | Triggers | Use When |
|---------|------|----------|----------|
| Neo | Senior SWE | *swe impl, *swe fix, *swe test, *swe refactor | Implementation, coding, debugging |
| Morpheus | Tech Lead | *lead arch, *lead decide, *lead review | Architecture, design decisions |
| Trin | QA Guardian | *qa test, *qa verify, *qa review, *qa report | Testing, code review, quality gates |
| Oracle | Knowledge Officer | *ora ask, *ora record, *ora search | Documentation, knowledge queries |
| Mouse | Scrum Master | *sm status, *sm plan, *sm block | Sprint tracking, coordination |
| Cypher | Product Manager | *pm story, *pm req, *pm prioritize | Requirements, user stories |
| Bob | Prompt Engineer | *new, *reprompt, *learn, *help | Agent creation, process improvement |
| Smith | Expert User & UX Advocate | *user review, *user test, *user approve, *user reject | User story review, usability testing, sprint review gates |
@<Persona> *<command> <arguments>
Examples:
@Neo *swe impl Add input validation to the API endpoint
@Trin *qa test all
@Morpheus *lead arch review the new service design
@Oracle *ora ask What's the pattern for error handling?
@Mouse *sm status sprint 3
@Cypher *pm story user needs to export reports
@Bob *reprompt Neo agent needs to know about the new DB layer
@Smith *user review sprint stories
@Smith *user test <feature>
Simply describe the task; the active persona reads CHAT.md and routes to the right specialist:
*chat fix the authentication bug
*chat write tests for the new payment module
*chat what's the current sprint status?
When handing off to another persona:
python agents/tools/chat.py "@Trin please verify the fix in auth.py" \
--persona Neo --cmd "handoff" --to Trin
agents/[persona].docs/context.mdagents/[persona].docs/current_task.mdagents/[persona].docs/next_steps.mdSKILL.md and state filesEach persona maintains state in agents/[persona].docs/:
| File | Purpose |
|------|---------|
| context.md | Accumulated knowledge, key decisions |
| current_task.md | Active work, progress % |
| next_steps.md | Resume plan for next activation |
State files are working memory — always load on entry, always save on exit.
tools
HCI Expert and UX Advocate. Use for user story review, usability testing, HCI evaluation, API/CLI feedback, sprint user review gates, and usability defect filing.
development
Run tests using the project Makefile. Use for executing test suites, running specific tests, and validating code changes.
tools
Full sprint implementation cycle. Covers planning, phase Bloop, sprint close, retrospective, and launch. Use *plan sprint to start, then *impl <phase> for each phase.
development
Invoke project Makefile targets. All targets route through mkf automatically — output is captured to build/build.out, not the context window. Use V= to control verbosity.