arthai-marketplace

/welcome

Role-aware welcome for non-engineers. Presents intent-based menu instead of blank terminal.

Synopsis

/welcome

When to use it

Quickstart

/welcome

What you’ll see: a short menu of 4 outcome-oriented options tailored to your role (e.g. “Plan a feature”, “Check project status”, “Something else”). Pick one and the right workflow runs — no jargon, no agent or model names, no slash-command syntax required.

Examples

/welcome      # the only form — the menu adapts to your stored or detected role

You may also see this menu appear automatically — without typing /welcome — on your first message if it’s a vague greeting like “hey” or “what should I do?” and your role resolves to non-engineer, or right after an engineer runs project setup and stores your role. That’s the same skill routing you in; it’s not an error.

What it does

  1. Detects your role — reads USER_ROLE from .claude/.claude-agents.conf; if absent, infers it from which specialist agents are installed in the project (e.g. a GTM agent without QA agents suggests PM/founder/marketer; design-studio agents without backend agents suggest designer; every category installed suggests engineer). If it still can’t tell, it asks via AskUserQuestion (“What’s your role on this team?” — Product Manager / Founder / Designer / Marketer / Operations / Engineer) — a user-confirmation checkpoint. The answer is stored so future sessions skip the question.
  2. Presents a role-based menu (user-confirmation checkpoint) — an AskUserQuestion with 4 options per role:
    • PM: Plan a feature · Check project status · Create or review an issue · Something else
    • Founder: Plan a feature or strategy · Check project status · Review positioning or GTM · Something else
    • Designer: Design thinking session · Get a design critique · Plan a UI feature · Something else
    • Marketer: Create a launch strategy · Analyze positioning · Plan content or campaign · Something else
    • Ops: Check project status · Triage open issues · Review recent changes · Something else
    • Engineer / unknown: falls through to /onboard
  3. Routes your choice — planning options ask you to type a feature name and a short brief in plain English, then invoke /planning with a design spec included by default (founders get --gtm; add --no-design if you want to skip the design spec); status options invoke /onboard; issue options list GitHub issues; positioning/launch/content and design options bring in the matching specialist with project context. “Something else” lets you describe what you need in plain English. Max one question before action — if you type something specific at any point, the menu gets out of the way.
  4. Offers follow-ups — after the routed action completes: “share this”, “revise [section]”, or “do something else” to return to the menu.

Output & artifacts

Troubleshooting

Problem Fix
It went straight to an engineer briefing Your role resolved to Engineer (or couldn’t be determined as a non-engineer role) — welcome hands engineers to /onboard by design
It guessed my role wrong Edit USER_ROLE in .claude/.claude-agents.conf — use one of pm, founder, designer, marketer, ops, or engineer (lowercase, e.g. USER_ROLE="pm") — and run /welcome again
None of the menu options fit Pick “Something else” and describe what you need — the menu is a suggestion, not a constraint