Add missing repository components for complete supercharge.sh installation
Added all directories and files expected by supercharge.sh: - hooks/ (5 hook scripts for session management and AI consultation) - commands/ (3 custom slash commands: brainstorm, write-plan, execute-plan) - plugins/ (plugin references for glm-plan, rust-analyzer, marketplaces) - bin/ralphloop (Ralph Orchestrator wrapper for autonomous iteration) - scripts/sync-agents.sh (agent synchronization script) - templates/ (config templates: settings, hooks, config.json) This completes the repository structure so supercharge.sh can install all components without warnings. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
44
commands/brainstorm.md
Normal file
44
commands/brainstorm.md
Normal file
@@ -0,0 +1,44 @@
|
||||
# /brainstorm
|
||||
|
||||
Multi-AI brainstorming session with Ralph integration.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/brainstorm "Design a feature for user authentication"
|
||||
```
|
||||
|
||||
## Description
|
||||
|
||||
Launches a collaborative brainstorming session using multiple AI perspectives:
|
||||
- Claude (primary)
|
||||
- Qwen (consultation)
|
||||
- Ralph Orchestrator (autonomous iteration)
|
||||
|
||||
## Modes
|
||||
|
||||
**Direct Mode** (simple tasks):
|
||||
- Quick ideation
|
||||
- Feature exploration
|
||||
- Design discussions
|
||||
|
||||
**Ralph Mode** (complex tasks):
|
||||
- Architecture design
|
||||
- System planning
|
||||
- Multi-phase projects
|
||||
|
||||
## Environment Variables
|
||||
|
||||
```bash
|
||||
QWEN_CONSULT_MODE=always|delegate|off
|
||||
RALPH_AUTO=true|false
|
||||
QWEN_MAX_ITERATIONS=3
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/brainstorm "How should we structure the API?"
|
||||
/brainstorm "Design a notification system"
|
||||
/brainstorm "Plan the database schema"
|
||||
```
|
||||
52
commands/execute-plan.md
Normal file
52
commands/execute-plan.md
Normal file
@@ -0,0 +1,52 @@
|
||||
# /execute-plan
|
||||
|
||||
Execute a previously created implementation plan.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/execute-plan
|
||||
/execute-plan my-plan.md
|
||||
/execute-plan --review
|
||||
```
|
||||
|
||||
## Description
|
||||
|
||||
Executes implementation plans created with `/write-plan`:
|
||||
- Reads plan from `.claude/plans/`
|
||||
- Executes each step in order
|
||||
- Creates checkpoints for rollback
|
||||
- Validates each step completion
|
||||
|
||||
## Options
|
||||
|
||||
```
|
||||
--review # Review plan before executing
|
||||
--from=N # Start from step N
|
||||
--to=N # Execute through step N
|
||||
--dry-run # Show what would be done
|
||||
--continue # Continue after error
|
||||
```
|
||||
|
||||
## Execution Process
|
||||
|
||||
1. **Load Plan** - Read and parse plan file
|
||||
2. **Review** (optional) - Show steps and confirm
|
||||
3. **Execute** - Run each step sequentially
|
||||
4. **Validate** - Verify each step completed
|
||||
5. **Checkpoint** - Save progress after each step
|
||||
6. **Report** - Summary of changes
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/execute-plan # Execute latest plan
|
||||
/execute-plan auth-plan.md # Execute specific plan
|
||||
/execute-plan --review # Review before executing
|
||||
/execute-plan --from=5 # Start from step 5
|
||||
```
|
||||
|
||||
## Checkpoints
|
||||
|
||||
Each step creates a checkpoint in `.claude/plans/<plan-name>.checkpoint/`
|
||||
Use `--continue` to resume from last checkpoint after failure.
|
||||
40
commands/write-plan.md
Normal file
40
commands/write-plan.md
Normal file
@@ -0,0 +1,40 @@
|
||||
# /write-plan
|
||||
|
||||
Create implementation plans from requirements or specifications.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/write-plan "Add user authentication with OAuth"
|
||||
```
|
||||
|
||||
## Description
|
||||
|
||||
Creates detailed, step-by-step implementation plans including:
|
||||
- Technical approach
|
||||
- File changes needed
|
||||
- Testing strategy
|
||||
- Dependencies
|
||||
- Risks and mitigations
|
||||
|
||||
## Plan Structure
|
||||
|
||||
1. **Summary** - High-level overview
|
||||
2. **Technical Approach** - Architecture decisions
|
||||
3. **Implementation Steps** - Ordered task list
|
||||
4. **Files to Create/Modify** - Specific files
|
||||
5. **Testing Strategy** - Validation approach
|
||||
6. **Dependencies** - Required packages/changes
|
||||
7. **Risks & Mitigations** - Potential issues
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/write-plan "Implement Stripe subscriptions"
|
||||
/write-plan "Add real-time notifications with WebSockets"
|
||||
/write-plan "Migrate from REST to GraphQL"
|
||||
```
|
||||
|
||||
## Output
|
||||
|
||||
Saves plan to `.claude/plans/` directory for later execution with `/execute-plan`.
|
||||
Reference in New Issue
Block a user