Strategic Claude Basic CLI is a command-line tool that simplifies the integration of the Strategic Claude Basic framework into any project. It automates the process of cloning the strategic-claude-base repository, copying its contents, and setting up the necessary directory structure and symlinks for Claude Code integration.
- Provide a simple, reliable way to add Strategic Claude Basic to any project
- Automate the complex setup process of directory structures and symlinks
- Enable easy management and cleanup of Strategic Claude Basic installations
- Support standard CLI patterns and shell completions
- Software Developers: Using Claude Code for development and wanting to add Strategic Claude Basic capabilities
- Project Maintainers: Setting up consistent Claude Code configurations across repositories
- DevOps Engineers: Automating development environment setup
User Story: As a developer, I want to add Strategic Claude Basic to my project with a single command so I can start using its features immediately.
Acceptance Criteria:
- Clone strategic-claude-base repository to temporary location
- Copy
.strategic-claude-basicdirectory to target project - Create
.claudedirectory if it doesn't exist - Set up symlinks from
.claudesubdirectories (agents/, commands/, hooks/) to strategic-claude-basic core components - Clean up temporary files
- Provide clear feedback on success/failure
User Story: As a developer with an existing Strategic Claude Basic installation, I want to update the core framework content without losing my project-specific customizations.
Acceptance Criteria:
- Selectively replace only framework directories (core, guides, templates)
- Preserve user directories (archives, issues, plan, research, summary)
- Maintain existing symlinks and configuration
- Provide clear feedback on what was updated vs. preserved
User Story: As a developer, I want to verify that Strategic Claude Basic is properly installed and configured in my project.
Acceptance Criteria:
- Check if
.strategic-claude-basicdirectory exists - Verify symlinks are valid and point to correct locations
- Display current installation state clearly
- Identify any configuration issues
User Story: As a project maintainer, I want to cleanly remove Strategic Claude Basic from a project when it's no longer needed.
Acceptance Criteria:
- Remove
.strategic-claude-basicdirectory - Remove strategic-claude symlinks from
.claudesubdirectories - Optionally clean up empty
.claudedirectory - Provide confirmation before destructive operations
User Story: As a CLI user, I want tab completion for commands and flags to improve my productivity.
Acceptance Criteria:
- Generate completion scripts for bash, zsh, fish, powershell
- Support completion of command names and flags
- Provide installation instructions for completions
Purpose: Initialize Strategic Claude Basic in a project
Flags:
--target, -t: Target directory (default: current directory)--force, -f: Overwrite existing installation completely--force-core: Update only framework directories (core, guides, templates) while preserving user content (archives, issues, plan, research, summary)--yes, -y: Skip confirmation prompt (auto-confirm installation)--no-backup: Skip backup creation--verbose, -v: Verbose output
Behavior:
- Validate target directory exists and is writable
- Check for existing installation (unless
--forceor--force-core) - Display installation summary and prompt for confirmation (unless
--yes):Target directory: /path/to/project Installation type: [New Installation | Update Core Only | Full Overwrite] This will install Strategic Claude Basic in the above directory. Are you sure you want to proceed? (y/N): - Create backup of existing files (unless
--no-backup) - Clone strategic-claude-base repository
- Copy
.strategic-claude-basicto target:- If
--force-core: Only replace core/, guides/, templates/ directories (preserve archives/, issues/, plan/, research/, summary/) - If
--force: Replace entire directory - Otherwise: Full installation (fail if exists)
- If
- Create
.claudedirectory structure (agents/, commands/, hooks/ subdirectories) - Set up symlinks:
.claude/agents/strategic→../.strategic-claude-basic/core/agents.claude/commands/strategic→../.strategic-claude-basic/core/commands.claude/hooks/strategic→../.strategic-claude-basic/core/hooks
- Validate installation
- Clean up temporary files
Purpose: Remove Strategic Claude Basic from a project
Flags:
--target, -t: Target directory (default: current directory)--force, -f: Skip confirmation prompts--verbose, -v: Verbose output
Behavior:
- Validate target directory
- Check for existing installation
- Prompt for confirmation (unless
--force) - Remove symlinks
- Remove
.strategic-claude-basicdirectory - Clean up empty
.claudedirectories if appropriate
Purpose: Display installation status
Flags:
--target, -t: Target directory (default: current directory)
Behavior:
- Check if
.strategic-claude-basicexists - Verify symlink integrity
- Display installation status with clear indicators
- Report any issues found
Purpose: Generate shell completion scripts
Arguments:
shell: Shell type (bash|zsh|fish|powershell)
Behavior:
- Generate appropriate completion script for specified shell
- Output to stdout for easy installation
- Provide installation instructions
- Git installed and available in PATH
- Go 1.21+ for building from source
- Write permissions to target directories
- Strategic Claude Basic content is pinned to a specific commit hash
- All installations use the same framework version until CLI is updated
- Framework updates require new CLI releases for consistency
- No user-configurable version selection to maintain stability
- Init command should complete within 30 seconds on typical network
- Status check should be near-instantaneous
- Minimal resource usage
- Clear, actionable error messages
- Graceful handling of network issues
- Proper cleanup on interruption
- Non-zero exit codes for failures
- User-friendly confirmation prompts with clear defaults
- Interactive confirmation prevents accidental installations
- Clear indication of installation type and target directory
--yesflag enables automation while maintaining safety by default
- Users can successfully initialize Strategic Claude Basic in under 30 seconds
- Zero failed installations due to permission or symlink issues
- Clear documentation and help text for all commands
- Shell completions work across major shells
- Complex configuration management beyond basic installation
- Integration with other Claude frameworks
- GUI interface
- Automatic updates of strategic-claude-base content