superclaude-kiro 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +190 -0
- package/bin/superclaude-kiro.js +38 -0
- package/dist/agents/sc-analyze.json +18 -0
- package/dist/agents/sc-implement.json +18 -0
- package/dist/agents/sc-pm.json +18 -0
- package/dist/agents/superclaude.json +18 -0
- package/dist/mcp/mcp-servers.json +44 -0
- package/dist/steering/superclaude/sc-agent.md +80 -0
- package/dist/steering/superclaude/sc-analyze.md +89 -0
- package/dist/steering/superclaude/sc-brainstorm.md +100 -0
- package/dist/steering/superclaude/sc-build.md +94 -0
- package/dist/steering/superclaude/sc-business-panel.md +90 -0
- package/dist/steering/superclaude/sc-cleanup.md +93 -0
- package/dist/steering/superclaude/sc-design.md +88 -0
- package/dist/steering/superclaude/sc-document.md +88 -0
- package/dist/steering/superclaude/sc-estimate.md +86 -0
- package/dist/steering/superclaude/sc-explain.md +92 -0
- package/dist/steering/superclaude/sc-git.md +80 -0
- package/dist/steering/superclaude/sc-help.md +148 -0
- package/dist/steering/superclaude/sc-implement.md +97 -0
- package/dist/steering/superclaude/sc-improve.md +93 -0
- package/dist/steering/superclaude/sc-index-repo.md +169 -0
- package/dist/steering/superclaude/sc-index.md +86 -0
- package/dist/steering/superclaude/sc-load.md +93 -0
- package/dist/steering/superclaude/sc-pm.md +592 -0
- package/dist/steering/superclaude/sc-recommend.md +1008 -0
- package/dist/steering/superclaude/sc-reflect.md +87 -0
- package/dist/steering/superclaude/sc-research.md +103 -0
- package/dist/steering/superclaude/sc-save.md +93 -0
- package/dist/steering/superclaude/sc-sc.md +134 -0
- package/dist/steering/superclaude/sc-select-tool.md +86 -0
- package/dist/steering/superclaude/sc-spawn.md +85 -0
- package/dist/steering/superclaude/sc-spec-panel.md +428 -0
- package/dist/steering/superclaude/sc-task.md +89 -0
- package/dist/steering/superclaude/sc-test.md +93 -0
- package/dist/steering/superclaude/sc-troubleshoot.md +88 -0
- package/dist/steering/superclaude/sc-workflow.md +97 -0
- package/package.json +52 -0
- package/src/cli.js +23 -0
- package/src/converter.js +63 -0
- package/src/installer.js +319 -0
- package/src/utils.js +105 -0
- package/templates/cli-settings.json +7 -0
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
---
|
|
2
|
+
inclusion: manual
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# SuperClaude: reflect
|
|
6
|
+
|
|
7
|
+
> Converted from Claude Code SuperClaude framework
|
|
8
|
+
> Original: ~/.claude/commands/sc/reflect.md
|
|
9
|
+
|
|
10
|
+
# /sc:reflect - Task Reflection and Validation
|
|
11
|
+
|
|
12
|
+
## Triggers
|
|
13
|
+
- Task completion requiring validation and quality assessment
|
|
14
|
+
- Session progress analysis and reflection on work accomplished
|
|
15
|
+
- Cross-session learning and insight capture for project improvement
|
|
16
|
+
- Quality gates requiring comprehensive task adherence verification
|
|
17
|
+
|
|
18
|
+
## Usage
|
|
19
|
+
```
|
|
20
|
+
/sc:reflect [--type task|session|completion] [--analyze] [--validate]
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Behavioral Flow
|
|
24
|
+
1. **Analyze**: Examine current task state and session progress using Serena reflection tools
|
|
25
|
+
2. **Validate**: Assess task adherence, completion quality, and requirement fulfillment
|
|
26
|
+
3. **Reflect**: Apply deep analysis of collected information and session insights
|
|
27
|
+
4. **Document**: Update session metadata and capture learning insights
|
|
28
|
+
5. **Optimize**: Provide recommendations for process improvement and quality enhancement
|
|
29
|
+
|
|
30
|
+
Key behaviors:
|
|
31
|
+
- Serena MCP integration for comprehensive reflection analysis and task validation
|
|
32
|
+
- Bridge between TodoWrite patterns and advanced Serena analysis capabilities
|
|
33
|
+
- Session lifecycle integration with cross-session persistence and learning capture
|
|
34
|
+
- Performance-critical operations with <200ms core reflection and validation
|
|
35
|
+
## MCP Integration
|
|
36
|
+
- **Serena MCP**: Mandatory integration for reflection analysis, task validation, and session metadata
|
|
37
|
+
- **Reflection Tools**: think_about_task_adherence, think_about_collected_information, think_about_whether_you_are_done
|
|
38
|
+
- **Memory Operations**: Cross-session persistence with read_memory, write_memory, list_memories
|
|
39
|
+
- **Performance Critical**: <200ms for core reflection operations, <1s for checkpoint creation
|
|
40
|
+
|
|
41
|
+
## Tool Coordination
|
|
42
|
+
- **TodoRead/TodoWrite**: Bridge between traditional task management and advanced reflection analysis
|
|
43
|
+
- **think_about_task_adherence**: Validates current approach against project goals and session objectives
|
|
44
|
+
- **think_about_collected_information**: Analyzes session work and information gathering completeness
|
|
45
|
+
- **think_about_whether_you_are_done**: Evaluates task completion criteria and remaining work identification
|
|
46
|
+
- **Memory Tools**: Session metadata updates and cross-session learning capture
|
|
47
|
+
|
|
48
|
+
## Key Patterns
|
|
49
|
+
- **Task Validation**: Current approach → goal alignment → deviation identification → course correction
|
|
50
|
+
- **Session Analysis**: Information gathering → completeness assessment → quality evaluation → insight capture
|
|
51
|
+
- **Completion Assessment**: Progress evaluation → completion criteria → remaining work → decision validation
|
|
52
|
+
- **Cross-Session Learning**: Reflection insights → memory persistence → enhanced project understanding
|
|
53
|
+
|
|
54
|
+
## Examples
|
|
55
|
+
|
|
56
|
+
### Task Adherence Reflection
|
|
57
|
+
```
|
|
58
|
+
/sc:reflect --type task --analyze
|
|
59
|
+
# Validates current approach against project goals
|
|
60
|
+
# Identifies deviations and provides course correction recommendations
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
### Session Progress Analysis
|
|
64
|
+
```
|
|
65
|
+
/sc:reflect --type session --validate
|
|
66
|
+
# Comprehensive analysis of session work and information gathering
|
|
67
|
+
# Quality assessment and gap identification for project improvement
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
### Completion Validation
|
|
71
|
+
```
|
|
72
|
+
/sc:reflect --type completion
|
|
73
|
+
# Evaluates task completion criteria against actual progress
|
|
74
|
+
# Determines readiness for task completion and identifies remaining blockers
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
## Boundaries
|
|
78
|
+
|
|
79
|
+
**Will:**
|
|
80
|
+
- Perform comprehensive task reflection and validation using Serena MCP analysis tools
|
|
81
|
+
- Bridge TodoWrite patterns with advanced reflection capabilities for enhanced task management
|
|
82
|
+
- Provide cross-session learning capture and session lifecycle integration
|
|
83
|
+
|
|
84
|
+
**Will Not:**
|
|
85
|
+
- Operate without proper Serena MCP integration and reflection tool access
|
|
86
|
+
- Override task completion decisions without proper adherence and quality validation
|
|
87
|
+
- Bypass session integrity checks and cross-session persistence requirements
|
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
---
|
|
2
|
+
inclusion: manual
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# SuperClaude: research
|
|
6
|
+
|
|
7
|
+
> Converted from Claude Code SuperClaude framework
|
|
8
|
+
> Original: ~/.claude/commands/sc/research.md
|
|
9
|
+
|
|
10
|
+
# /sc:research - Deep Research Command
|
|
11
|
+
|
|
12
|
+
> **Context Framework Note**: This command activates comprehensive research capabilities with adaptive planning, multi-hop reasoning, and evidence-based synthesis.
|
|
13
|
+
|
|
14
|
+
## Triggers
|
|
15
|
+
- Research questions beyond knowledge cutoff
|
|
16
|
+
- Complex research questions
|
|
17
|
+
- Current events and real-time information
|
|
18
|
+
- Academic or technical research requirements
|
|
19
|
+
- Market analysis and competitive intelligence
|
|
20
|
+
|
|
21
|
+
## Context Trigger Pattern
|
|
22
|
+
```
|
|
23
|
+
/sc:research "[query]" [--depth quick|standard|deep|exhaustive] [--strategy planning|intent|unified]
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
## Behavioral Flow
|
|
27
|
+
|
|
28
|
+
### 1. Understand (5-10% effort)
|
|
29
|
+
- Assess query complexity and ambiguity
|
|
30
|
+
- Identify required information types
|
|
31
|
+
- Determine resource requirements
|
|
32
|
+
- Define success criteria
|
|
33
|
+
|
|
34
|
+
### 2. Plan (10-15% effort)
|
|
35
|
+
- Select planning strategy based on complexity
|
|
36
|
+
- Identify parallelization opportunities
|
|
37
|
+
- Generate research question decomposition
|
|
38
|
+
- Create investigation milestones
|
|
39
|
+
|
|
40
|
+
### 3. TodoWrite (5% effort)
|
|
41
|
+
- Create adaptive task hierarchy
|
|
42
|
+
- Scale tasks to query complexity (3-15 tasks)
|
|
43
|
+
- Establish task dependencies
|
|
44
|
+
- Set progress tracking
|
|
45
|
+
|
|
46
|
+
### 4. Execute (50-60% effort)
|
|
47
|
+
- **Parallel-first searches**: Always batch similar queries
|
|
48
|
+
- **Smart extraction**: Route by content complexity
|
|
49
|
+
- **Multi-hop exploration**: Follow entity and concept chains
|
|
50
|
+
- **Evidence collection**: Track sources and confidence
|
|
51
|
+
|
|
52
|
+
### 5. Track (Continuous)
|
|
53
|
+
- Monitor TodoWrite progress
|
|
54
|
+
- Update confidence scores
|
|
55
|
+
- Log successful patterns
|
|
56
|
+
- Identify information gaps
|
|
57
|
+
|
|
58
|
+
### 6. Validate (10-15% effort)
|
|
59
|
+
- Verify evidence chains
|
|
60
|
+
- Check source credibility
|
|
61
|
+
- Resolve contradictions
|
|
62
|
+
- Ensure completeness
|
|
63
|
+
|
|
64
|
+
## Key Patterns
|
|
65
|
+
|
|
66
|
+
### Parallel Execution
|
|
67
|
+
- Batch all independent searches
|
|
68
|
+
- Run concurrent extractions
|
|
69
|
+
- Only sequential for dependencies
|
|
70
|
+
|
|
71
|
+
### Evidence Management
|
|
72
|
+
- Track search results
|
|
73
|
+
- Provide clear citations when available
|
|
74
|
+
- Note uncertainties explicitly
|
|
75
|
+
|
|
76
|
+
### Adaptive Depth
|
|
77
|
+
- **Quick**: Basic search, 1 hop, summary output
|
|
78
|
+
- **Standard**: Extended search, 2-3 hops, structured report
|
|
79
|
+
- **Deep**: Comprehensive search, 3-4 hops, detailed analysis
|
|
80
|
+
- **Exhaustive**: Maximum depth, 5 hops, complete investigation
|
|
81
|
+
|
|
82
|
+
## MCP Integration
|
|
83
|
+
- **Tavily**: Primary search and extraction engine
|
|
84
|
+
- **Sequential**: Complex reasoning and synthesis
|
|
85
|
+
- **Playwright**: JavaScript-heavy content extraction
|
|
86
|
+
- **Serena**: Research session persistence
|
|
87
|
+
|
|
88
|
+
## Output Standards
|
|
89
|
+
- Save reports to `claudedocs/research_[topic]_[timestamp].md`
|
|
90
|
+
- Include executive summary
|
|
91
|
+
- Provide confidence levels
|
|
92
|
+
- List all sources with citations
|
|
93
|
+
|
|
94
|
+
## Examples
|
|
95
|
+
```
|
|
96
|
+
/sc:research "latest developments in quantum computing 2024"
|
|
97
|
+
/sc:research "competitive analysis of AI coding assistants" --depth deep
|
|
98
|
+
/sc:research "best practices for distributed systems" --strategy unified
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
## Boundaries
|
|
102
|
+
**Will**: Current information, intelligent search, evidence-based analysis
|
|
103
|
+
**Won't**: Make claims without sources, skip validation, access restricted content
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
---
|
|
2
|
+
inclusion: manual
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# SuperClaude: save
|
|
6
|
+
|
|
7
|
+
> Converted from Claude Code SuperClaude framework
|
|
8
|
+
> Original: ~/.claude/commands/sc/save.md
|
|
9
|
+
|
|
10
|
+
# /sc:save - Session Context Persistence
|
|
11
|
+
|
|
12
|
+
## Triggers
|
|
13
|
+
- Session completion and project context persistence needs
|
|
14
|
+
- Cross-session memory management and checkpoint creation requests
|
|
15
|
+
- Project understanding preservation and discovery archival scenarios
|
|
16
|
+
- Session lifecycle management and progress tracking requirements
|
|
17
|
+
|
|
18
|
+
## Usage
|
|
19
|
+
```
|
|
20
|
+
/sc:save [--type session|learnings|context|all] [--summarize] [--checkpoint]
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Behavioral Flow
|
|
24
|
+
1. **Analyze**: Examine session progress and identify discoveries worth preserving
|
|
25
|
+
2. **Persist**: Save session context and learnings using Serena MCP memory management
|
|
26
|
+
3. **Checkpoint**: Create recovery points for complex sessions and progress tracking
|
|
27
|
+
4. **Validate**: Ensure session data integrity and cross-session compatibility
|
|
28
|
+
5. **Prepare**: Ready session context for seamless continuation in future sessions
|
|
29
|
+
|
|
30
|
+
Key behaviors:
|
|
31
|
+
- Serena MCP integration for memory management and cross-session persistence
|
|
32
|
+
- Automatic checkpoint creation based on session progress and critical tasks
|
|
33
|
+
- Session context preservation with comprehensive discovery and pattern archival
|
|
34
|
+
- Cross-session learning with accumulated project insights and technical decisions
|
|
35
|
+
|
|
36
|
+
## MCP Integration
|
|
37
|
+
- **Serena MCP**: Mandatory integration for session management, memory operations, and cross-session persistence
|
|
38
|
+
- **Memory Operations**: Session context storage, checkpoint creation, and discovery archival
|
|
39
|
+
- **Performance Critical**: <200ms for memory operations, <1s for checkpoint creation
|
|
40
|
+
|
|
41
|
+
## Tool Coordination
|
|
42
|
+
- **write_memory/read_memory**: Core session context persistence and retrieval
|
|
43
|
+
- **think_about_collected_information**: Session analysis and discovery identification
|
|
44
|
+
- **summarize_changes**: Session summary generation and progress documentation
|
|
45
|
+
- **TodoRead**: Task completion tracking for automatic checkpoint triggers
|
|
46
|
+
|
|
47
|
+
## Key Patterns
|
|
48
|
+
- **Session Preservation**: Discovery analysis → memory persistence → checkpoint creation
|
|
49
|
+
- **Cross-Session Learning**: Context accumulation → pattern archival → enhanced project understanding
|
|
50
|
+
- **Progress Tracking**: Task completion → automatic checkpoints → session continuity
|
|
51
|
+
- **Recovery Planning**: State preservation → checkpoint validation → restoration readiness
|
|
52
|
+
|
|
53
|
+
## Examples
|
|
54
|
+
|
|
55
|
+
### Basic Session Save
|
|
56
|
+
```
|
|
57
|
+
/sc:save
|
|
58
|
+
# Saves current session discoveries and context to Serena MCP
|
|
59
|
+
# Automatically creates checkpoint if session exceeds 30 minutes
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
### Comprehensive Session Checkpoint
|
|
63
|
+
```
|
|
64
|
+
/sc:save --type all --checkpoint
|
|
65
|
+
# Complete session preservation with recovery checkpoint
|
|
66
|
+
# Includes all learnings, context, and progress for session restoration
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
### Session Summary Generation
|
|
70
|
+
```
|
|
71
|
+
/sc:save --summarize
|
|
72
|
+
# Creates session summary with discovery documentation
|
|
73
|
+
# Updates cross-session learning patterns and project insights
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
### Discovery-Only Persistence
|
|
77
|
+
```
|
|
78
|
+
/sc:save --type learnings
|
|
79
|
+
# Saves only new patterns and insights discovered during session
|
|
80
|
+
# Updates project understanding without full session preservation
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
## Boundaries
|
|
84
|
+
|
|
85
|
+
**Will:**
|
|
86
|
+
- Save session context using Serena MCP integration for cross-session persistence
|
|
87
|
+
- Create automatic checkpoints based on session progress and task completion
|
|
88
|
+
- Preserve discoveries and patterns for enhanced project understanding
|
|
89
|
+
|
|
90
|
+
**Will Not:**
|
|
91
|
+
- Operate without proper Serena MCP integration and memory access
|
|
92
|
+
- Save session data without validation and integrity verification
|
|
93
|
+
- Override existing session context without proper checkpoint preservation
|
|
@@ -0,0 +1,134 @@
|
|
|
1
|
+
---
|
|
2
|
+
inclusion: manual
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# SuperClaude: sc
|
|
6
|
+
|
|
7
|
+
> Converted from Claude Code SuperClaude framework
|
|
8
|
+
> Original: ~/.claude/commands/sc/sc.md
|
|
9
|
+
|
|
10
|
+
# SuperClaude Command Dispatcher
|
|
11
|
+
|
|
12
|
+
🚀 **SuperClaude Framework** - Main command dispatcher
|
|
13
|
+
|
|
14
|
+
## Usage
|
|
15
|
+
|
|
16
|
+
All SuperClaude commands use the `/sc:` prefix:
|
|
17
|
+
|
|
18
|
+
```
|
|
19
|
+
/sc:command [args...]
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
## Available Commands
|
|
23
|
+
|
|
24
|
+
### Research & Analysis
|
|
25
|
+
```
|
|
26
|
+
/sc:research [query] - Deep web research with parallel search
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
### Repository Management
|
|
30
|
+
```
|
|
31
|
+
/sc:index-repo - Index repository for context optimization
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
### AI Agents
|
|
35
|
+
```
|
|
36
|
+
/sc:agent [type] - Launch specialized AI agents
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
### Recommendations
|
|
40
|
+
```
|
|
41
|
+
/sc:recommend [context] - Get command recommendations
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
### Help
|
|
45
|
+
```
|
|
46
|
+
/sc - Show this help (all available commands)
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
## Command Namespace
|
|
50
|
+
|
|
51
|
+
All commands are namespaced under `sc:` to keep them organized:
|
|
52
|
+
- ✅ `/sc:research query`
|
|
53
|
+
- ✅ `/sc:index-repo`
|
|
54
|
+
- ✅ `/sc:agent type`
|
|
55
|
+
- ✅ `/sc:recommend`
|
|
56
|
+
- ✅ `/sc` (help)
|
|
57
|
+
|
|
58
|
+
## Examples
|
|
59
|
+
|
|
60
|
+
### Research
|
|
61
|
+
```
|
|
62
|
+
/sc:research React 18 new features
|
|
63
|
+
/sc:research LLM agent architectures 2024
|
|
64
|
+
/sc:research Python async best practices
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
### Index Repository
|
|
68
|
+
```
|
|
69
|
+
/sc:index-repo
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
### Agent
|
|
73
|
+
```
|
|
74
|
+
/sc:agent deep-research
|
|
75
|
+
/sc:agent self-review
|
|
76
|
+
/sc:agent repo-index
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
### Recommendations
|
|
80
|
+
```
|
|
81
|
+
/sc:recommend
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
## Quick Reference
|
|
85
|
+
|
|
86
|
+
| Command | Description | Example |
|
|
87
|
+
|---------|-------------|---------|
|
|
88
|
+
| `/sc:research` | Deep web research | `/sc:research topic` |
|
|
89
|
+
| `/sc:index-repo` | Repository indexing | `/sc:index-repo` |
|
|
90
|
+
| `/sc:agent` | Specialized AI agents | `/sc:agent type` |
|
|
91
|
+
| `/sc:recommend` | Command suggestions | `/sc:recommend` |
|
|
92
|
+
| `/sc` | Show help | `/sc` |
|
|
93
|
+
|
|
94
|
+
## Features
|
|
95
|
+
|
|
96
|
+
- **Parallel Execution**: Research runs multiple searches in parallel
|
|
97
|
+
- **Evidence-Based**: All findings backed by sources
|
|
98
|
+
- **Context-Aware**: Uses repository context when available
|
|
99
|
+
- **Token Efficient**: Optimized for minimal token usage
|
|
100
|
+
|
|
101
|
+
## Help
|
|
102
|
+
|
|
103
|
+
For help on specific commands:
|
|
104
|
+
```
|
|
105
|
+
/sc:research --help
|
|
106
|
+
/sc:agent --help
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
Or use the main help command:
|
|
110
|
+
```
|
|
111
|
+
/sc
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
Check the documentation:
|
|
115
|
+
- PLANNING.md - Architecture and design
|
|
116
|
+
- TASK.md - Current tasks and priorities
|
|
117
|
+
- KNOWLEDGE.md - Tips and best practices
|
|
118
|
+
|
|
119
|
+
## Version
|
|
120
|
+
|
|
121
|
+
SuperClaude v4.1.7
|
|
122
|
+
- Python package: 0.4.0
|
|
123
|
+
- Pytest plugin included
|
|
124
|
+
- PM Agent patterns enabled
|
|
125
|
+
|
|
126
|
+
---
|
|
127
|
+
|
|
128
|
+
💡 **Tip**: All commands use the `/sc:` prefix - e.g., `/sc:research`, `/sc:agent`
|
|
129
|
+
|
|
130
|
+
🔧 **Installation**: Run `superclaude install` to install/update commands
|
|
131
|
+
|
|
132
|
+
📚 **Documentation**: https://github.com/SuperClaude-Org/SuperClaude_Framework
|
|
133
|
+
|
|
134
|
+
⚠️ **Important**: Restart Claude Code after installing commands to use them!
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
---
|
|
2
|
+
inclusion: manual
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# SuperClaude: select-tool
|
|
6
|
+
|
|
7
|
+
> Converted from Claude Code SuperClaude framework
|
|
8
|
+
> Original: ~/.claude/commands/sc/select-tool.md
|
|
9
|
+
|
|
10
|
+
# /sc:select-tool - Intelligent MCP Tool Selection
|
|
11
|
+
|
|
12
|
+
## Triggers
|
|
13
|
+
- Operations requiring optimal MCP tool selection between Serena and Morphllm
|
|
14
|
+
- Meta-system decisions needing complexity analysis and capability matching
|
|
15
|
+
- Tool routing decisions requiring performance vs accuracy trade-offs
|
|
16
|
+
- Operations benefiting from intelligent tool capability assessment
|
|
17
|
+
|
|
18
|
+
## Usage
|
|
19
|
+
```
|
|
20
|
+
/sc:select-tool [operation] [--analyze] [--explain]
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Behavioral Flow
|
|
24
|
+
1. **Parse**: Analyze operation type, scope, file count, and complexity indicators
|
|
25
|
+
2. **Score**: Apply multi-dimensional complexity scoring across various operation factors
|
|
26
|
+
3. **Match**: Compare operation requirements against Serena and Morphllm capabilities
|
|
27
|
+
4. **Select**: Choose optimal tool based on scoring matrix and performance requirements
|
|
28
|
+
5. **Validate**: Verify selection accuracy and provide confidence metrics
|
|
29
|
+
|
|
30
|
+
Key behaviors:
|
|
31
|
+
- Complexity scoring based on file count, operation type, language, and framework requirements
|
|
32
|
+
- Performance assessment evaluating speed vs accuracy trade-offs for optimal selection
|
|
33
|
+
- Decision logic matrix with direct mappings and threshold-based routing rules
|
|
34
|
+
- Tool capability matching for Serena (semantic operations) vs Morphllm (pattern operations)
|
|
35
|
+
|
|
36
|
+
## MCP Integration
|
|
37
|
+
- **Serena MCP**: Optimal for semantic operations, LSP functionality, symbol navigation, and project context
|
|
38
|
+
- **Morphllm MCP**: Optimal for pattern-based edits, bulk transformations, and speed-critical operations
|
|
39
|
+
- **Decision Matrix**: Intelligent routing based on complexity scoring and operation characteristics
|
|
40
|
+
|
|
41
|
+
## Tool Coordination
|
|
42
|
+
- **get_current_config**: System configuration analysis for tool capability assessment
|
|
43
|
+
- **execute_sketched_edit**: Operation testing and validation for selection accuracy
|
|
44
|
+
- **Read/Grep**: Operation context analysis and complexity factor identification
|
|
45
|
+
- **Integration**: Automatic selection logic used by refactor, edit, implement, and improve commands
|
|
46
|
+
|
|
47
|
+
## Key Patterns
|
|
48
|
+
- **Direct Mapping**: Symbol operations → Serena, Pattern edits → Morphllm, Memory operations → Serena
|
|
49
|
+
- **Complexity Thresholds**: Score >0.6 → Serena, Score <0.4 → Morphllm, 0.4-0.6 → Feature-based
|
|
50
|
+
- **Performance Trade-offs**: Speed requirements → Morphllm, Accuracy requirements → Serena
|
|
51
|
+
- **Fallback Strategy**: Serena → Morphllm → Native tools degradation chain
|
|
52
|
+
|
|
53
|
+
## Examples
|
|
54
|
+
|
|
55
|
+
### Complex Refactoring Operation
|
|
56
|
+
```
|
|
57
|
+
/sc:select-tool "rename function across 10 files" --analyze
|
|
58
|
+
# Analysis: High complexity (multi-file, symbol operations)
|
|
59
|
+
# Selection: Serena MCP (LSP capabilities, semantic understanding)
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
### Pattern-Based Bulk Edit
|
|
63
|
+
```
|
|
64
|
+
/sc:select-tool "update console.log to logger.info across project" --explain
|
|
65
|
+
# Analysis: Pattern-based transformation, speed priority
|
|
66
|
+
# Selection: Morphllm MCP (pattern matching, bulk operations)
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
### Memory Management Operation
|
|
70
|
+
```
|
|
71
|
+
/sc:select-tool "save project context and discoveries"
|
|
72
|
+
# Direct mapping: Memory operations → Serena MCP
|
|
73
|
+
# Rationale: Project context and cross-session persistence
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
## Boundaries
|
|
77
|
+
|
|
78
|
+
**Will:**
|
|
79
|
+
- Analyze operations and provide optimal tool selection between Serena and Morphllm
|
|
80
|
+
- Apply complexity scoring based on file count, operation type, and requirements
|
|
81
|
+
- Provide sub-100ms decision time with >95% selection accuracy
|
|
82
|
+
|
|
83
|
+
**Will Not:**
|
|
84
|
+
- Override explicit tool specifications when user has clear preference
|
|
85
|
+
- Select tools without proper complexity analysis and capability matching
|
|
86
|
+
- Compromise performance requirements for convenience or speed
|
|
@@ -0,0 +1,85 @@
|
|
|
1
|
+
---
|
|
2
|
+
inclusion: manual
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# SuperClaude: spawn
|
|
6
|
+
|
|
7
|
+
> Converted from Claude Code SuperClaude framework
|
|
8
|
+
> Original: ~/.claude/commands/sc/spawn.md
|
|
9
|
+
|
|
10
|
+
# /sc:spawn - Meta-System Task Orchestration
|
|
11
|
+
|
|
12
|
+
## Triggers
|
|
13
|
+
- Complex multi-domain operations requiring intelligent task breakdown
|
|
14
|
+
- Large-scale system operations spanning multiple technical areas
|
|
15
|
+
- Operations requiring parallel coordination and dependency management
|
|
16
|
+
- Meta-level orchestration beyond standard command capabilities
|
|
17
|
+
|
|
18
|
+
## Usage
|
|
19
|
+
```
|
|
20
|
+
/sc:spawn [complex-task] [--strategy sequential|parallel|adaptive] [--depth normal|deep]
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Behavioral Flow
|
|
24
|
+
1. **Analyze**: Parse complex operation requirements and assess scope across domains
|
|
25
|
+
2. **Decompose**: Break down operation into coordinated subtask hierarchies
|
|
26
|
+
3. **Orchestrate**: Execute tasks using optimal coordination strategy (parallel/sequential)
|
|
27
|
+
4. **Monitor**: Track progress across task hierarchies with dependency management
|
|
28
|
+
5. **Integrate**: Aggregate results and provide comprehensive orchestration summary
|
|
29
|
+
|
|
30
|
+
Key behaviors:
|
|
31
|
+
- Meta-system task decomposition with Epic → Story → Task → Subtask breakdown
|
|
32
|
+
- Intelligent coordination strategy selection based on operation characteristics
|
|
33
|
+
- Cross-domain operation management with parallel and sequential execution patterns
|
|
34
|
+
- Advanced dependency analysis and resource optimization across task hierarchies
|
|
35
|
+
## MCP Integration
|
|
36
|
+
- **Native Orchestration**: Meta-system command uses native coordination without MCP dependencies
|
|
37
|
+
- **Progressive Integration**: Coordination with systematic execution for progressive enhancement
|
|
38
|
+
- **Framework Integration**: Advanced integration with SuperClaude orchestration layers
|
|
39
|
+
|
|
40
|
+
## Tool Coordination
|
|
41
|
+
- **TodoWrite**: Hierarchical task breakdown and progress tracking across Epic → Story → Task levels
|
|
42
|
+
- **Read/Grep/Glob**: System analysis and dependency mapping for complex operations
|
|
43
|
+
- **Edit/MultiEdit/Write**: Coordinated file operations with parallel and sequential execution
|
|
44
|
+
- **Bash**: System-level operations coordination with intelligent resource management
|
|
45
|
+
|
|
46
|
+
## Key Patterns
|
|
47
|
+
- **Hierarchical Breakdown**: Epic-level operations → Story coordination → Task execution → Subtask granularity
|
|
48
|
+
- **Strategy Selection**: Sequential (dependency-ordered) → Parallel (independent) → Adaptive (dynamic)
|
|
49
|
+
- **Meta-System Coordination**: Cross-domain operations → resource optimization → result integration
|
|
50
|
+
- **Progressive Enhancement**: Systematic execution → quality gates → comprehensive validation
|
|
51
|
+
|
|
52
|
+
## Examples
|
|
53
|
+
|
|
54
|
+
### Complex Feature Implementation
|
|
55
|
+
```
|
|
56
|
+
/sc:spawn "implement user authentication system"
|
|
57
|
+
# Breakdown: Database design → Backend API → Frontend UI → Testing
|
|
58
|
+
# Coordinates across multiple domains with dependency management
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
### Large-Scale System Operation
|
|
62
|
+
```
|
|
63
|
+
/sc:spawn "migrate legacy monolith to microservices" --strategy adaptive --depth deep
|
|
64
|
+
# Enterprise-scale operation with sophisticated orchestration
|
|
65
|
+
# Adaptive coordination based on operation characteristics
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
### Cross-Domain Infrastructure
|
|
69
|
+
```
|
|
70
|
+
/sc:spawn "establish CI/CD pipeline with security scanning"
|
|
71
|
+
# System-wide infrastructure operation spanning DevOps, Security, Quality domains
|
|
72
|
+
# Parallel execution of independent components with validation gates
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
## Boundaries
|
|
76
|
+
|
|
77
|
+
**Will:**
|
|
78
|
+
- Decompose complex multi-domain operations into coordinated task hierarchies
|
|
79
|
+
- Provide intelligent orchestration with parallel and sequential coordination strategies
|
|
80
|
+
- Execute meta-system operations beyond standard command capabilities
|
|
81
|
+
|
|
82
|
+
**Will Not:**
|
|
83
|
+
- Replace domain-specific commands for simple operations
|
|
84
|
+
- Override user coordination preferences or execution strategies
|
|
85
|
+
- Execute operations without proper dependency analysis and validation
|