init
Initialize project documentation, preferences, or design tokens
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/marcusgoll/Spec-Flow/HEAD/.claude/commands/core/init.md -o ~/.claude/commands/init.mdinit.md
# /init — Consolidated Project Initialization <context> **Arguments**: $ARGUMENTS </context> <objective> Unified entry point for project initialization. Routes to specialized commands: - `/init` → Project documentation (8 docs via interactive questionnaire) - `/init --preferences` → User preference configuration - `/init --tokens` → Design token generation (OKLCH + WCAG) All flags are passed through to the underlying commands. </objective> <process> ## Step 1: Parse Arguments and Route **Check $ARGUMENTS for routing:** 1. **If `--preferences` flag present:** ``` Extract: Remove --preferences from arguments Route to: /project/init-preferences $remaining_args ``` 2. **If `--tokens` flag present:** ``` Extract: Remove --tokens from arguments Route to: /project/init-tokens $remaining_args ``` 3. **Otherwise (default):** ``` Route to: /project/init-project $ARGUMENTS ``` ## Step 2: Execute Routed Command Use SlashCommand tool to invoke the appropriate active command with all arguments passed through. **For preferences:** ``` SlashCommand: /project/init-preferences [remaining args] ``` **For tokens:** ``` SlashCommand: /project/init-tokens [remaining args] ``` **For project (default):** ``` SlashCommand: /project/init-project [all args] ``` </process> <success_criteria> - Correct command identified from flags - All arguments passed through properly - Underlying command executes successfully </success_criteria> --- ## Quick Reference | Command | Purpose | |---------|---------| | `/init` | Generate 8 project docs (interactive) | | `/init --preferences` | Configure command defaults | | `/init --tokens` | Generate OKLCH design tokens | | `/init --with-design` | Project docs + design system | | `/init --ci` | Non-interactive mode for CI/CD |
Execute multiple sprints in parallel based on dependency graph from sprint-plan.md
Build and validate locally for projects without remote deployment (prototypes, experiments, local-only dev)
Execute multi-sprint epic workflow from interactive scoping through deployment with parallel sprint execution and self-improvement
Execute feature development workflow from specification through production deployment with automated quality gates
Analyze workflow state and provide context-aware guidance with visual progress indicators and recommended next steps
Implement small bug fixes and features (<100 LOC) without full workflow. Use for single-file changes, bug fixes, refactors, and minor enhancements that can be completed in under 30 minutes.
Enter deep craftsman mode - question everything, plan like Da Vinci, craft insanely great solutions, then materialize to roadmap
Display Vercel and Railway deployment quota usage with 24h rolling window analysis, quota reset predictions, and deployment strategy recommendations