[fxmaxvl]

What

New skill /bf:kit <purpose>. It builds a standalone, git-initialised Claude Code plugin (a "kit") for one domain, such as a CTO-course kit with skills for strategy analysis, strategy plans, decks, and CTO reviews.

A kit is made of:

• Main context (context/main.md): purpose, perspective, frameworks, output style, terminology, and the one-question-per-turn rule. Every kit skill reads it first.
• Knowledge (knowledge/): course notes, slides, and URLs, distilled and indexed.
• Utility skills that let the kit grow itself without bf: write-skill (picks up BACKLOG.md), adopt-skill, and update-context.
• Domain skills, agreed in the build session. You pick which to draft now; the rest go to the backlog.

How

• skills/kit/scripts/kit-scaffold.sh has two modes:
  • probe checks for a non-empty target, an enclosing repo, and a git identity.
  • create renders the templates, writes plugin.json plus a local marketplace.json ("source": "."), and runs git init.
• templates/skill-skeleton.md is read with the Read tool, not inlined into write-skill. Inlined, ${CLAUDE_PLUGIN_ROOT} gets expanded when the skill loads, and later skills would be pinned to an absolute path.
• Phase 7 greps for bf references, unrendered placeholders, and hard-coded kit paths, runs claude plugin validate, then makes the initial commit.
• plugin-main.md: bf:kit is added to the named exceptions for writing outside .bf/.
• The README table gets a new row. Version goes to 1.39.0.

Tested

• The scaffold probe and create modes work, including the non-empty-target and bad-name error paths.
• claude plugin validate passes on a generated kit with no warnings.
• The self-containment and absolute-path greps come back clean on a fresh kit and catch planted violations.
• claude --plugin-dir <kit> -p … discovers cto-course:write-skill, adopt-skill, and update-context.
• Not yet run: a full interactive /bf:kit session.