Stats
Actions
Tags
From ai-agents-workflow
Bootstrap <artifact-root>/config/PROJECT_CONFIG.md for this repo via the init agent.
How this command is triggered — by the user, by Claude, or both
Slash command
/ai-agents-workflow:init [--force]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Dispatch the `init` subagent to bootstrap the consumer repo's project configuration. Use the Task tool with `subagent_type: ai-agents-workflow:init` and pass this prompt to the agent: The init agent will: 1. **Resolve or pick the artifact layout.** If neither `./.claude/aiaw-data-<project>/` nor `../aiaw-data-<project>/` exists, ask which layout to use: - **In-project** — `./.claude/aiaw-data-<project>/` (default, no permission grant needed). - **Sibling** — `../aiaw-data-<project>/` (merges one entry into `<project>/.claude/settings.local.json`, which is gitignored). If a leg...
Dispatch the init subagent to bootstrap the consumer repo's project configuration.
Use the Task tool with subagent_type: ai-agents-workflow:init and pass this prompt to the agent:
init $ARGUMENTS
The init agent will:
./.claude/aiaw-data-<project>/ nor ../aiaw-data-<project>/ exists, ask which layout to use:
./.claude/aiaw-data-<project>/ (default, no permission grant needed).../aiaw-data-<project>/ (merges one entry into <project>/.claude/settings.local.json, which is gitignored).
If a legacy ./ai-workflow-data/ folder is present, the agent refuses to proceed and directs you to the README's Migration section.project-discovery skill (non-mutating ecosystem scan).AskUserQuestion for any ambiguous classification.project-config-review review-and-comment gate (loops on user comments until explicit approval).<artifact-root>/config/PROJECT_CONFIG.md and ensure <artifact-root>/tasks/.gitkeep exists.If the file already exists and --force was not passed, the agent will exit with already initialized. --force rewrites only PROJECT_CONFIG.md (and the derived context cache); it does not change the artifact layout. To switch layouts (e.g. in-project → sibling), mv the folder manually per the README Migration section before re-running init --force. On a fresh project (no artifact folder yet), --force does not bypass the Step 0 layout question — it still appears once.
npx claudepluginhub kingsharkg/ai-agents-workflow --plugin ai-agents-workflow/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.