菜单
File a new work item into wiki/backlog/inbox/. Use whenever the user reports a bug, asks for a feature, or proposes a change of direction mid-run — instead of inline-patching. Any agent (including subagents) can invoke this. Triggered by /intake "<title>" or when an agent recognises new work that should be captured.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Primary entry point for a freshly cloned Vibin seed repo. Interviews the user about the project, stack, package manager, constraints, and initial backlog, populates the wiki/ starter pages, scaffolds the chosen stack, writes the stack-specific permission profile, and hands off to the manager skill. Use when starting a new project, or when the user says "bootstrap", "set up the project", or "let's begin".
One-question-at-a-time interviewing discipline that drives /bootstrap and /intake to ~95% confidence before writing the wiki or an item card. Use when gathering requirements for a new project or fleshing out a vague work item.
Orchestrates Vibin's wiki-driven, spec-driven, test-first build pipeline. The top-level session runs this skill to order the backlog and drive the spec-writer -> test-writer -> implementer -> reviewer pipeline (or the bug / research / chore tracks), one item at a time. Use after /bootstrap, or to resume building the backlog.
Bring an existing Vibin project up to date with the latest seed by diffing the project's recorded seed commit against the latest Vibin on GitHub and applying the changes. Use when the user says "migrate", "migrate-vibin", "upgrade Vibin", "apply the latest seed changes", or after a new seed release. Reads the seed commit hash from .vibin-version, audits the project's actual state, applies the migrations added since, and reconciles seed-owned files while preserving local customizations.
Reference for the red-green-refactor test-first discipline used by the test-writer and implementer agents. Use when you need the canonical explanation of how Vibin's tests-first workflow works, or to settle a question about test ordering, "minimum" code, or trivially-passing tests.
One-screen summary of where the manager pipeline is — lane counts, the active item with its current stage, the last escalation if any, and the next three ready items. Read-only. Use any time you want to know what's happening without disturbing a running pipeline.
| name | intake |
| description | File a new work item into wiki/backlog/inbox/. Use whenever the user reports a bug, asks for a feature, or proposes a change of direction mid-run — instead of inline-patching. Any agent (including subagents) can invoke this. Triggered by /intake "<title>" or when an agent recognises new work that should be captured. |
| disable-model-invocation | false |
This skill captures new work as a per-item file in wiki/backlog/inbox/ so it goes
through the normal triage → spec → tests → impl → review flow instead of being
inline-patched in whatever was happening at the time. See CLAUDE.md → Triage.
Safe for any agent to invoke: it only reads the wiki and writes one new file under
wiki/backlog/inbox/. It does not spawn other agents and does not touch other items.
Read wiki/INDEX.md and wiki/backlog/README.md (the item card schema). A
PreToolUse hook blocks writes until you have.
Take the title from the /intake "<title>" argument if present. Then use
AskUserQuestion to fill in the rest, with these questions and defaults:
feature (default) / bug / research / chore. If the user said
"bug" or "broken" in the title, default to bug. If the title is a question,
default to research.high / medium (default) / low.flags: [review] so the manager
pauses for approval before tests/impl. Default to yes for bug (regression risk)
and for any item the user describes as architectural/risky.full (default) / lite. Suggest lite for an obviously
trivial, behavior-neutral ask (copy/text, CSS, a trivial config tweak) that touches few
files, changes no schema/API, and isn't security-sensitive; the user can set or veto it. A
bug is never lite. This is only a hint — the manager re-checks the lite gate and
silently runs full (or auto-promotes mid-flight) if it doesn't qualify, so a wrong guess is
caught, not relied on. Record mode: lite in the card; omit the field for full.A clearly-specified ask files in one shot — don't add friction where there's none. For a
vague item, follow the interview discipline in .claude/skills/interview/SKILL.md: ask the
one or two adaptive questions that make it actionable, then file. If invoked by another agent
mid-task, take whatever fields the agent provides and only ask the user for the rest.
Scan wiki/backlog/**/*.md with Glob. Parse each filename for the B<n>- prefix.
The next id is max + 1 (or B1 if no items exist). Slug the title:
lowercase, spaces → hyphens, strip punctuation, cap at ~40 chars.
Write wiki/backlog/inbox/B<n>-<slug>.md:
---
id: B<n>
title: <title>
type: <type>
priority: <priority>
flags: <[review] | []>
mode: lite # OMIT this line for full (the default)
created: <today YYYY-MM-DD>
---
## Description
<the description from step 2, or "(to be elaborated by spec-writer)">
## Notes
Do not link this file from wiki/INDEX.md — the backlog directory is already linked
via wiki/backlog/README.md. Individual item files are not separately indexed.
Tell the caller (user or invoking agent):
Filed B: <title> as
<type>inwiki/backlog/inbox/B<n>-<slug>.md(priority:<priority>, flags:[…]).
If the manager is mid-pipeline on another item, that item continues. The new item
sits in inbox/ until the manager triages it on its next planning pass.