From product-forge
Initialize the local cards directory structure for Product Forge.
How this command is triggered — by the user, by Claude, or both
Slash command
/product-forge:initThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /init Command Initialize the local `cards/` directory structure at the project root. This is a prerequisite for all Product Forge commands. The command is idempotent and safe to run multiple times. ## Execution When invoked, this command: 1. **Creates the cards directory structure** by creating all 7 required subdirectories under `cards/`: - cards/initiatives/ - cards/epics/ - cards/stories/ - cards/intakes/ - cards/checkpoints/ - cards/decisions/ - cards/release-notes/ 2. **Creates index.json files** in each subdirectory using forge-lib (for fast querying) 3. *...
Initialize the local cards/ directory structure at the project root. This is a prerequisite for all Product Forge commands. The command is idempotent and safe to run multiple times.
When invoked, this command:
Creates the cards directory structure by creating all 7 required subdirectories under cards/:
Creates index.json files in each subdirectory using forge-lib (for fast querying)
Reports results to the user:
Initialize using forge-lib CLI:
forge card init --directory .
Parse the JSON response:
{
"success": true,
"data": {
"directories_created": [
"cards/initiatives",
"cards/epics",
"cards/stories",
"cards/intakes",
"cards/checkpoints",
"cards/decisions",
"cards/release-notes"
],
"index_files_created": 7
}
}
If forge-lib returns an error:
{
"success": false,
"data": null,
"error": "Permission denied: cannot create directory cards/"
}
Report the error to the user:
Error initializing cards directory: {error message from JSON response}
Check that the working directory is writable and you're running from the project root.
/init multiple times has no side effects. It only creates directories that don't already exist.After successful initialization, display:
Cards directory initialized. Ready for card creation.
Use /product-forge:create to generate cards (auto-detects type) or specify with --type.
npx claudepluginhub jeremybrice/the-forge --plugin product-forge/camp-initCreates a new campaign workspace with standard directory structure (projects, festivals, workflow, docs, .campaign). Also sets up shell integration.
/pac-configureInitializes a Product as Code (PAC) project: creates .pac/ directory with epics/tickets/templates subdirs, pac.config.yaml, templates, and initial epic/ticket files.
/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.