ワンクリックで
template
One-sentence summary of what this skill does. Start with a verb, keep it specific enough that Claude can decide when to invoke it.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
One-sentence summary of what this skill does. Start with a verb, keep it specific enough that Claude can decide when to invoke it.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Relentless goal/design interview that sharpens framing and writes durable docs (brainstorm artifact, ADRs, glossary) as decisions crystallize. Use when refining a flywheel goal, pressure-testing scope, or "grill with docs".
Start or resume the full agentic coding flywheel. Drives the complete workflow: scan → discover → plan → implement → review.
Set up flywheel prerequisites for this project.
One-shot diagnostic of every flywheel dependency — MCP connectivity, Agent Mail liveness, br/bv/ntm/cm binaries, node version, git status, dist-drift, orphaned worktrees, and checkpoint validity. Use when debugging toolchain issues, before starting a new session, after /flywheel-cleanup, or as a CI gate.
Strategic gap analysis between vision (AGENTS.md / README.md / plan docs) and what's actually implemented. Converts gaps into beads, optionally launches a swarm. Use when "reality check", "where are we really", "gap analysis", "did we drift", or before declaring a long-running project done.
Launch a parallel swarm of agents to implement multiple beads simultaneously.
| name | _template |
| description | One-sentence summary of what this skill does. Start with a verb, keep it specific enough that Claude can decide when to invoke it. |
<One-paragraph framing of what this skill does and why. Reference $ARGUMENTS
if the skill accepts them.>
<Instructions. Cite the exact tool names: Bash, Read, Edit, AskUserQuestion,
and any MCP tool as tool_name (e.g. flywheel_doctor).>
<Instructions.>
<Instructions. If the skill terminates with a user decision, use
AskUserQuestion — never free-text prompts. See UNIVERSAL RULE 1 in
skills/start/SKILL.md.>
If your skill calls flywheel_* MCP tools, route on
result.structuredContent?.data?.error?.code rather than parsing
error.message. Surface error.hint inline — it is the user's next step.