Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From dt-workspace
Initialize dt-workspace project configuration. Creates .dt-workspace config file with project settings.
npx claudepluginhub deepaktiwari09/dt-workspace-plugin --plugin dt-workspaceHow this command is triggered — by the user, by Claude, or both
Slash command
/dt-workspace:init [project-name]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
# Initialize DT-Workspace Project Initialize a new dt-workspace configuration for documentation generation. ## Steps 1. **Check for existing config**: Look for `.dt-workspace` file in current directory 2. **If exists**: Ask user if they want to overwrite 3. **Gather information** using AskUserQuestion: - Project name (default: directory name or argument) - SOW file path (default: ./sow.md) - Preset selection (microservices/monolith/serverless/supabase/firebase/nextjs-fullstack/graphql-federation/kubernetes/event-sourcing) - Output directory (default: ./workflows) 4. **Create...
/toolkit-initInitializes project with ai-toolkit structure (53 files), smartly detecting new setup or update/sync mode. Minimal questions for new projects; supports --force and --dry-run.
/initInitializes docs folder with minimal, standard, or full structure, creating directories and README files with navigation, placeholders, and project analysis. Supports --check preview and --force overwrite.
/setupInteractively onboards project: gathers business goals via questions, scans codebase for structure and tech, creates .claude/project-goals.md and project-map.md.
/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/init-projectInitializes project by interactively generating CLAUDE.md (overview, stack, structure), spec.md (feature specs), and prompt_plan.md (phased implementation plan). Auto-detects tech stack; supports [name] [--type next|vite|go|python|rust].
/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.
Share bugs, ideas, or general feedback.
Initialize a new dt-workspace configuration for documentation generation.
Check for existing config: Look for .dt-workspace file in current directory
If exists: Ask user if they want to overwrite
Gather information using AskUserQuestion:
Create .dt-workspace file:
{
"version": "1.0.0",
"projectName": "<from user>",
"sowPath": "<from user>",
"defaultPreset": "<from user>",
"outputDirectory": "<from user>",
"generatedAt": "<ISO timestamp>",
"generatedPaths": {
"platforms": {}
}
}
Verify SOW file exists: Check if sowPath file exists, warn if not
Display summary:
DT-WORKSPACE INITIALIZED
Configuration: .dt-workspace
Project: <name>
SOW Path: <path>
Preset: <preset>
Output: <directory>
Next steps:
1. Ensure SOW file exists at <sowPath>
2. Run /dt-workspace:scaffold to generate documentation