teamcraft-glgd:onboard

---
name: teamcraft-glgd:onboard
description: Orient a new team member to their environment through the TeamCraft lens. Reads GitLab repos, active milestones, open issues, and Google Drive project artifacts — then presents the current state and explains how TeamCraft applies to their role. Advisory only. Never starts work.
argument-hint: "(no arguments)"
disable-model-invocation: true
user-invocable: true
allowed-tools:
  - mcp__gitlab__list_projects
  - mcp__gitlab__get_project
  - mcp__gitlab__list_milestones
  - mcp__gitlab__list_issues
  - mcp__google-drive__list_accounts
  - mcp__google-drive__search_files
  - mcp__google-drive__download_file
  - mcp__google-drive__list_folder
  - AskUserQuestion
---

## Goal

Read the team member's environment and present it through the TeamCraft lens. Show them what exists, describe the current state, and explain how TeamCraft applies to their role going forward. This is orientation — not a handoff to work.

## Hard Constraints

- **Read-only. Advisory only.** This skill observes and explains. It never offers to create, update, or run any workflow. It never says "want me to help you work on that?" The session ends at orientation.
- Google Drive and GitLab connections are verified through real tool calls, not by asking.
- If a Drive file operation fails with a path error, read the error message to identify a valid accessible host path and retry with it.
- This is Cowork compatible — no local filesystem tools are used.
- The moment a sentence begins with "shall I" or "want me to" — stop. That is out of scope.

## Establish Role

Ask the team member their role. Everything that follows is calibrated to it.

- **Developer** — build loop, issue work, code, MRs
- **Product Manager** — requirements, sprint planning, visibility
- **Tech Lead / Architect** — decisions, conventions, code review
- **QA Analyst** — sprint awareness, test prep, bug capture
- **DevOps Engineer** — CI/CD setup and health

If they don't have a role or want the full picture, give the overview for all roles.

## Verify Connections

Attempt real calls. Do not ask whether things are configured.

**GitLab:** Use `mcp__gitlab__list_projects`. If it returns results, the server is up and authenticated. If not, explain what needs to be configured — in plain terms appropriate to the role.

**Google Drive:** Call `mcp__google-drive__list_accounts`. Any response means the server is reachable. If no accounts are returned, Drive is reachable but no Google account has been authenticated — explain this to the team member in plain terms. If one account is returned, use it for this session. If multiple accounts are returned, present them and ask which one to use. Pass `account_email` on every Drive tool call for the remainder of this session. If a Drive call returns a permission error, surface it clearly and offer to try another account if one is available.

If either connection fails, do not attempt to guide through MCP setup here — that is `teamcraft-glgd:teamcraft-setup`'s job. Tell the user clearly: "One or more required MCP servers isn't connected. Run `teamcraft-glgd:teamcraft-setup` first — it will get everything configured and bring you back here when ready." Do not proceed to environment reading until both connections are working.

## Read the Environment

With connections confirmed, read what exists. The goal is breadth, not depth — understand the shape of the environment, not every detail.

**GitLab:**
- Surface what projects are visible. Ask the team member which one (or ones) they are joining.
- For the relevant project(s): fetch the active milestone if one exists. Get a count and brief summary of open issues — enough to describe the state of the sprint, not a full issue list.

**Google Drive:**
- Search for the project's key artifacts: PRD, tech decisions, conventions. If found, download and read enough to characterize their state — what phase they're in, how complete they appear, what they cover. Not a full summary — just enough to speak to their existence and maturity.
- If artifacts are missing or incomplete, note that clearly — it is relevant context for the orientation.

## Present What You Found

Give the team member a clear picture of what you can see:

- What projects exist and which one they're joining
- Whether a sprint is active, how many issues are open, rough shape of the backlog
- What Drive artifacts exist: which documents are there, what state they appear to be in, what is missing

Be direct. "You have an active sprint with 8 open issues and a PRD that covers the compression service scope. Tech decisions and conventions documents don't exist yet." That is more useful than a long qualified description.

## Advise Through the TeamCraft Lens

Now map what you found onto TeamCraft — for their role specifically.

The question to answer: given what exists in this environment right now, how does TeamCraft apply and where does this person fit?

- If there's an active sprint and they're a developer: "The build loop is your entry point. Issues are waiting. fetch-issue is how you begin."
- If there's a PRD but no sprint and they're a PM: "The PRD exists. The next step in the TeamCraft upstream flow is tech decisions — but if those are captured, plan-sprint is what turns the PRD into a GitLab milestone."
- If artifacts are missing and they're a tech lead: "Tech decisions and conventions aren't documented yet. Those are your first two artifacts in TeamCraft — and they flow directly into every developer's planning session."
- If it's early and little exists: describe what TeamCraft would build from here and in what order.

Explain the map. Don't offer to navigate it.

## Close

End with one sentence naming where this person would begin when they're ready to work — the specific skill, nothing more.

"When you're ready to start, `teamcraft-glgd:fetch-issue` is your entry point." Full stop. No offer to run it now.