$npx -y skills add omnigentx/jarvis --skill team-rosterTeam member roster, expertise, tools, and coordination guide. Read this skill to know who to ask for help and what they can do.
| 1 | # TEAM ROSTER |
| 2 | |
| 3 | ## Team Members & Capabilities |
| 4 | |
| 5 | | Agent | Role | Key Tools | Can Do | |
| 6 | |-------|------|-----------|--------| |
| 7 | | Linh - PM | Project Manager | email, agent_spawner, github, meeting_room | Spawn/manage team members, track progress, search GitHub issues/PRs, create meetings | |
| 8 | | Hoa - BA | Business Analyst | email, github, scrapling, figma-ui-mcp, meeting_room | Research requirements, browse web for references, read GitHub code, review Figma designs | |
| 9 | | Khang - SA | Solution Architect | email, github, scrapling, figma-ui-mcp, meeting_room | Design architecture, read/search GitHub repos, research tech via web, review Figma layouts | |
| 10 | | Minh - Dev | Developer | email, **git**, github, scrapling, figma-ui-mcp, meeting_room | **Clone/pull/push code via git**, implement features, read GitHub PRs, browse API docs | |
| 11 | | Trang - Designer | UI/UX Designer | email, **figma-ui-mcp**, meeting_room | **Create Figma designs** (pages, frames, components), design UI/UX flows, export assets | |
| 12 | | Tuan - QE | QA Engineer | email, github, scrapling, figma-ui-mcp, meeting_room | Write/run tests, read GitHub code, verify against Figma designs, browse test references | |
| 13 | | Duc - DSO | DevSecOps | email, **git**, github, scrapling, meeting_room | **Clone/pull/push code**, manage CI/CD pipelines, deploy, security review | |
| 14 | |
| 15 | <important_capabilities> |
| 16 | ## Who can do what — delegate accordingly! |
| 17 | |
| 18 | - **Need code in workspace?** → Ask **Minh - Dev** or **Duc - DSO** to `git clone` the repo |
| 19 | - **Need a Figma design?** → Ask **Trang - Designer** to create it with `figma-ui-mcp` |
| 20 | - **Need to read code on GitHub?** → **Linh - PM**, **Hoa - BA**, **Khang - SA**, **Minh - Dev**, **Tuan - QE**, **Duc - DSO** all have `github` tool |
| 21 | - **Need web research?** → **Hoa - BA**, **Khang - SA**, **Minh - Dev**, **Tuan - QE**, **Duc - DSO** have `scrapling` tool |
| 22 | - **Need to deploy/CI?** → Ask **Duc - DSO** |
| 23 | </important_capabilities> |
| 24 | |
| 25 | <communication_rules> |
| 26 | 1. Use `send_email`: `send_email(to="Minh - Dev", body="...", subject="...")` |
| 27 | 2. Emails from teammates are **auto-delivered** — no need to poll |
| 28 | 3. Wait for dependency: `send_email(to="Agent", body="Send me [deliverable] when ready", subject="[WAITING] ...")` |
| 29 | 4. Check status: `check_teammate_status(agent_name="Hoa - BA")` |
| 30 | 5. DO NOT guess — ASK teammates when uncertain |
| 31 | 6. DO NOT resend a message you already sent |
| 32 | 7. ALWAYS use agent display name — not role key (use "Hoa - BA" not "ba") |
| 33 | </communication_rules> |
| 34 | |
| 35 | <escalation_rules> |
| 36 | Escalate to PM when: |
| 37 | - Blocked more than 2 times by the same issue |
| 38 | - Scope has changed from the original plan |
| 39 | - Need a team member not yet in the team |
| 40 | - Discovered a risk affecting the timeline |
| 41 | </escalation_rules> |
| 42 | |
| 43 | ## Standard Workflow |
| 44 | |
| 45 | ``` |
| 46 | Linh - PM assigns → Hoa - BA writes BRD → Khang - SA reviews & designs |
| 47 | → Minh - Dev implements → Tuan - QE tests → Duc - DSO deploys |
| 48 | → Linh - PM wraps up |
| 49 | ``` |
| 50 | |
| 51 | > **Note**: Not every project needs all 7 members. |
| 52 | > PM decides which members participate based on scope. |