Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From elegance-pipeline
Initializes the elegance pipeline state manager for the repository by running a Python script with project anchor file and up to 4 scout scopes. Prompts for inputs if no arguments provided.
npx claudepluginhub ancplua/ancplua-claude-plugins --plugin elegance-pipelineHow this command is triggered — by the user, by Claude, or both
Slash command
/elegance-pipeline:initThe summary Claude sees in its command listing — used to decide when to auto-load this command
Initialize the elegance pipeline state manager. Run: If `$ARGUMENTS` is empty, ask the user for the project anchor file and 4 scout scopes. The project anchor is any meaningful root file (e.g., `CLAUDE.md`, `package.json`, `*.sln`). Scout scopes are directories that each scout will analyze independently. Use `--state-dir` when you want one isolated pipeline per spec instead of reusing the shared default state.
/initInitializes beads issue tracking database in current directory with optional prefix (defaults to dir name). Shows DB location, prefix, workflow overview, next steps; displays stats if already set up.
/initInitializes guided UI design for dashboards, apps, and tools. Assesses intent, proposes styles with rationale, builds components, and offers to save patterns.
/initSets up Repowise for the current codebase. Installs if needed, asks about indexing preferences (index-only or full with LLM), and runs the indexing process.
/initScaffolds a kubb.config.ts by running the Kubb init CLI. Accepts flags for an OpenAPI spec input, output directory, and comma-separated plugins.
/initDownloads and installs the notification binary for the claude-notifications plugin on macOS, Linux, or Windows, fetching the latest from GitHub Releases.
/initInitializes or re-boots llmdoc/ directory structure, runs multi-themed project investigations with investigator, and generates initial stable docs via recorder.
Share bugs, ideas, or general feedback.
Initialize the elegance pipeline state manager.
Run:
python ${CLAUDE_PLUGIN_ROOT}/elegance_pipeline/pipeline.py [--state-dir <dir>] init \
--project-anchor $ARGUMENTS \
--scope <scope-1> \
--scope <scope-2> \
--scope <scope-3> \
--scope <scope-4>
If $ARGUMENTS is empty, ask the user for the project anchor file and 4 scout scopes.
The project anchor is any meaningful root file (e.g., CLAUDE.md, package.json, *.sln).
Scout scopes are directories that each scout will analyze independently.
Use --state-dir when you want one isolated pipeline per spec instead of reusing the shared default state.