メニュー
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 ページを確認してインストールできます。
SOC 職業分類に基づく
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".
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.
Generate images via the Gemini MCP server (Imagen 4 family and Nano Banana family). Use this skill whenever the user wants to create, generate, design, or produce any image, illustration, icon, logo, hero, banner, mockup, diagram, screenshot stand-in, social card, poster, or other visual asset — even when they don't name a model and even when they phrase it casually ("I need an icon here", "make me a header image", "generate a thumbnail"). Use it for editing or iterating on previously generated images too. The skill picks the right model for the task, crafts a strong prompt, and saves the image into the project.
When the user wants to write, rewrite, or improve marketing copy for any page - including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.
| 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.Ask in a single batch of AskUserQuestion calls when invoked interactively; 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] | []>
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.