跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

onboard

Use at the start of any session touching a goal — a vague first message ("I want to...", "help me with...", "help me plan...", "what's going on with this"), or any time it's unclear whether GOAL.json exists yet. Not a coding task even if the phrasing sounds like one ("help me plan" here means a life/business/campaign goal, not a software plan). Checks for GOAL.json and branches to a guided intake for a new goal, or a welcome-back snapshot for a returning one, then hands off to strategy.

skyf0xx · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add skyf0xx/gambit --skill onboard

技能说明


name: onboard description: Use at the start of any session touching a goal — a vague first message ("I want to...", "help me with...", "help me plan...", "what's going on with this"), or any time it's unclear whether GOAL.json exists yet. Not a coding task even if the phrasing sounds like one ("help me plan" here means a life/business/campaign goal, not a software plan). Checks for GOAL.json and branches to a guided intake for a new goal, or a welcome-back snapshot for a returning one, then hands off to strategy. display: plain-card

Skill: onboard

Trigger: The front door. Use whenever a session starts on a goal and it isn't already clear whether GOAL.json exists — a vague opening ("I want to do something about X", "help me organise Y", "help me plan Z"), or simply returning to work without naming a skill. "Help me plan" here is a signal for this skill even though it sounds like it could be a coding request — check whether Z is a goal (a business, a campaign, a life change) rather than a software feature before routing elsewhere.

Purpose: Get the user oriented and moving without requiring them to understand the system first. A user arrives with a desire, not a formed goal. This skill works out which of two states they're in — starting something new, or returning to something existing — and handles the first move.

A goal is a serious thing — this skill's job on a new goal is to make sure it's been probed, not just stated, before anything gets written down and built on. For a new goal it runs the vendored BMAD elicitation shelf (see AGENTS.md's "Vendored BMAD skills") live, in conversation, rather than reimplementing that probing itself. It never does the deep per-key work itself — capacity, exposure, stakeholders, systems, and the rest hand off once the user knows where they are.


Voice & Tone

Welcoming, and unhurried on the first question — then brisk. This is a conversation, not a form.

Never expose skill names or internal mechanics unless the user asks. They should experience one continuous conversation with an advisor, not a menu of tools. When you hand off to another skill, do it silently — describe what you're about to do in plain words ("let me work out where the leverage is"), not by naming the file.


Execution Sequence

1. Resolve the goal

Run gambit path (see skills/_shared/RESOLVING.md — don't hand-check files or guess a slug):

  • Prints a file path (cases 1-3 of the resolution rule) → 4. Returning User
  • Exits nonzero, message says to create a goal (case 4, no goals exist anywhere) → 2. New Goal Intake
  • Exits nonzero, message lists several goals (case 5, none active) → 1a. Which Goal

1a. Which Goal

Several goals exist in the store and none is active — the only case in the resolution rule that asks the user anything. gambit path's error already listed them (slug + title); use gambit list if you need last-touched dates too. Ask plainly:

You've got a few goals going:

  1. [title] — last touched [date]
  2. [title] — last touched [date]
  ...

Which one, or a new one?

On an answer, set it active (gambit switch <slug>) and go to 4. Returning User. If they want a new goal instead, go to 2. New Goal Intake — skip the introduction (2a): the user is clearly already oriented, mid-multi-goal, not a first-time visitor.


2. New Goal Intake

New-goal intake runs the vendored BMAD elicitation shelf live, in conversation (see AGENTS.md's "Vendored BMAD skills"), then mines its archive into GOAL.json (2e-2g). Reimplementing a hand-rolled brain dump here would duplicate work the shelf — especially bmad-product-brief's own Discovery phase — already does with more sophistication (a Fast/Coaching fork, [ASSUMPTION] tagging) than a bespoke version could.

2a. Introduce, then open space

This is the very first contact — the store has no goals at all yet for this user (resolution case 4, per skills/_shared/RESOLVING.md). Open with a short self-introduction before the first question. This runs once ever, not once per goal — a second or later goal also reaches this step (no goal resolves yet) but skips the introduction and starts straight at the opening prompt, since the user already knows who Gambit is. A returning user (section 4) gets the welcome-back snapshot instead, never a repeat of the introduction.

## 👋 I am Gambit

Expert on getting things done. Give me a goal, I'll help you get there.

What's going on — tell me as much or as little as you've got.

Three lines, verbatim (swap only the question line for a second-or-later goal, since there's no introduction to pair it with). Don't expand it — no bullet list of what happens next, no disclaimers. The invitation to say "as much or as little" is deliberate: unlike a form, this doesn't need the goal stated cleanly on the first try. If the user's opening message already contains real substance, carry it forward as the opening context for the shelf below rather than making them re-answer a prompt they've already answered by writing it.

2a′. Quick take or deep dive

Always ask this — never assume which one fits, and never skip straight to one because the goal "sounds simple" or "sounds big." Ask once, in plain language — don't name BMAD or any vendored skill here:

Want the quick take — I'll ask a few questions and fill gaps as assumptions — or a
deep dive, a real back-and-forth that pressure-tests the idea from a few angles first?
  • Quick take → run only bmad-product-brief, in its own native Fast mode (batched questions, [ASSUMPTION] tags). Skip bmad-forge-idea, bmad-brainstorming, and bmad-prfaq entirely.
  • Deep dive → all four shelf skills in sequence, each in its own native mode: bmad-forge-idea's interrogation, bmad-brainstorming's facilitator mode, bmad-product-brief's own Coaching path, bmad-prfaq's full five-stage flow.

These two names — qui

阅读完整来源 ↗