From smurf
Scaffold the project-side files smurf needs (verify.sh, docs/rigor-level.md, .claude/runs/next-goal.md). Idempotent — running twice is a no-op.
How this command is triggered — by the user, by Claude, or both
Slash command
/smurf:initThe summary Claude sees in its command listing — used to decide when to auto-load this command
Smurf is loaded by reference from the installed plugin. The plugin
itself does not copy any file into your project. This command creates
the **minimum required project-side stubs** so the orchestrator can
operate. Existing files are never overwritten.
Run it now:
!`bash "${CLAUDE_PLUGIN_ROOT}/scripts/init-project.sh" "${CLAUDE_PROJECT_DIR:-$PWD}"`
After this completes:
1. Replace the no-op `verify.sh` body with your stack's
tests/build (npm test, pytest, cargo test, mvn verify, etc.).
2. Optionally copy `${CLAUDE_PLUGIN_ROOT}/policy.yaml` to
`.claude/policy.yaml` and edit `forbidd...Smurf is loaded by reference from the installed plugin. The plugin itself does not copy any file into your project. This command creates the minimum required project-side stubs so the orchestrator can operate. Existing files are never overwritten.
Run it now:
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/init-project.sh" "${CLAUDE_PROJECT_DIR:-$PWD}"
After this completes:
verify.sh body with your stack's
tests/build (npm test, pytest, cargo test, mvn verify, etc.).${CLAUDE_PLUGIN_ROOT}/policy.yaml to
.claude/policy.yaml and edit forbidden_paths /
forbidden_patterns for your project. Without an override the
plugin's defaults are used."env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" } to
.claude/settings.local.json..claude/runs/next-goal.md and run
/smurf:kickoff "<goal>" (or /smurf:kickoff-team for parallel
features).npx claudepluginhub abaddon/smurf --plugin smurf/initInitializes beads issue tracking in the current directory, creating a new database with an optional issue prefix. Shows database location, prefix, and guides next steps.
/initSets up Repowise for the codebase — checks installation, indexes dependencies, git history, and code health. Interactive mode selection with optional LLM-powered documentation generation.
/initInitializes ArcKit project structure for enterprise architecture governance, creating the projects/ directory with global policies and external reference folders.
/initScaffolds a Kubb config file and installs plugins by running the kubb init CLI with optional input spec, output dir, and plugin list arguments.
/initDownloads and installs the notification binary for the claude-notifications plugin, supporting macOS, Linux, and Windows.
/initInitializes or re-bootstraps the llmdoc documentation framework for a project, creating the directory skeleton, running investigations, and generating initial stable docs.