メニュー
One-screen v2 status — current sprint tasks + run log tail, backlog cards, knowledge-graph size. Read-only.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | status |
| description | One-screen v2 status — current sprint tasks + run log tail, backlog cards, knowledge-graph size. Read-only. |
| disable-model-invocation | false |
Report, in this order, nothing else:
wiki/sprint.md exists: its open tasks and the last ~5 run-log lines. If not:
"no active sprint".wiki/backlog/*.md (title, type, priority, flags). Flag any card marked
review or blocked.wiki/knowledge/<group>/ and the 3 most recently modified atoms
(ls -t).git status --short summary (counts only).Do not modify anything. Do not start work — that's the loop skill.
Primary entry point for a freshly cloned Vibin seed. Interviews the user, seeds the knowledge graph, scaffolds the stack, writes the permission profile, strips seed-meta, and hands off to the loop skill. Use when starting a new project, or when the user says "bootstrap" or "let's begin".
File a new work item as a card in wiki/backlog/ (v2 — card-is-spec, slug filename, proportional detail). Use whenever the user reports a bug, asks for a feature, or proposes new work mid-task — instead of inline-patching.
Run the Vibin v2 build loop — pull a work item into the sprint, then retrieve → do → verify → capture → review → close, mostly inline. Use to build the backlog or resume work.
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.
Run multiple sprints in parallel — partition backlog cards, create git worktrees per sprint, spawn background subagents, merge when done. Use when you want to parallelise independent concerns across concurrent sprints.
Execute a pre-composed sprint — retrieve, do, verify, capture, commit, close. No planning, no user checkpoints. Used by the loop skill after planning, and by the sprint-runner agent for parallel sprints.