Files
SuperClaude/plugins/superclaude/commands/reflect.md
mithun50 ab8904bc8c feat: restore all 30 slash commands with comprehensive documentation
Restored 26 additional commands from commit d4a17fc, bringing total from 5 to 30 commands.

## New Commands Added (26):
- /analyze - Code and architecture analysis
- /brainstorm - Structured brainstorming sessions
- /build - Build and compilation workflows
- /business-panel - Multi-expert business analysis
- /cleanup - Code cleanup and refactoring
- /design - System design and architecture
- /document - Documentation generation
- /estimate - Effort and time estimation
- /explain - Code explanation
- /git - Git operations and workflows
- /help - Command help and usage
- /implement - Implementation workflows
- /improve - Code improvement suggestions
- /index - Project indexing (alias for index-repo)
- /load - Load saved sessions
- /pm - Project management workflows
- /reflect - Reflection and retrospectives
- /save - Save current session
- /select-tool - Tool selection guidance
- /spawn - Spawn parallel tasks
- /spec-panel - Multi-expert specification analysis
- /task - Task management
- /test - Testing workflows
- /troubleshoot - Debugging and troubleshooting
- /workflow - Custom workflow automation

## Documentation Updates:
- Created docs/reference/commands-list.md with categorized command reference
- Updated README.md with expandable 30-command list
- Updated README-zh.md with Chinese translations
- Updated README-ja.md with Japanese translations
- Updated README-kr.md with Korean translations
- Changed statistics: "3 plugins" → "30 commands"
- Added command categories: Planning & Design, Development, Testing & Quality,
  Documentation, Version Control, Project Management, Research & Analysis, Utilities

## Files Changed:
- 60 files changed, 7930 insertions(+), 267 deletions(-)
- Added 26 commands to plugins/superclaude/commands/
- Added 26 commands to src/superclaude/commands/
- Created comprehensive command documentation

Commands restored from: d4a17fc (superclaude/commands/)
Total: 30 commands now available

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 16:08:56 +01:00

89 lines
3.9 KiB
Markdown

---
name: reflect
description: "Task reflection and validation using Serena MCP analysis capabilities"
category: special
complexity: standard
mcp-servers: [serena]
personas: []
---
# /sc:reflect - Task Reflection and Validation
## Triggers
- Task completion requiring validation and quality assessment
- Session progress analysis and reflection on work accomplished
- Cross-session learning and insight capture for project improvement
- Quality gates requiring comprehensive task adherence verification
## Usage
```
/sc:reflect [--type task|session|completion] [--analyze] [--validate]
```
## Behavioral Flow
1. **Analyze**: Examine current task state and session progress using Serena reflection tools
2. **Validate**: Assess task adherence, completion quality, and requirement fulfillment
3. **Reflect**: Apply deep analysis of collected information and session insights
4. **Document**: Update session metadata and capture learning insights
5. **Optimize**: Provide recommendations for process improvement and quality enhancement
Key behaviors:
- Serena MCP integration for comprehensive reflection analysis and task validation
- Bridge between TodoWrite patterns and advanced Serena analysis capabilities
- Session lifecycle integration with cross-session persistence and learning capture
- Performance-critical operations with <200ms core reflection and validation
## MCP Integration
- **Serena MCP**: Mandatory integration for reflection analysis, task validation, and session metadata
- **Reflection Tools**: think_about_task_adherence, think_about_collected_information, think_about_whether_you_are_done
- **Memory Operations**: Cross-session persistence with read_memory, write_memory, list_memories
- **Performance Critical**: <200ms for core reflection operations, <1s for checkpoint creation
## Tool Coordination
- **TodoRead/TodoWrite**: Bridge between traditional task management and advanced reflection analysis
- **think_about_task_adherence**: Validates current approach against project goals and session objectives
- **think_about_collected_information**: Analyzes session work and information gathering completeness
- **think_about_whether_you_are_done**: Evaluates task completion criteria and remaining work identification
- **Memory Tools**: Session metadata updates and cross-session learning capture
## Key Patterns
- **Task Validation**: Current approach → goal alignment → deviation identification → course correction
- **Session Analysis**: Information gathering → completeness assessment → quality evaluation → insight capture
- **Completion Assessment**: Progress evaluation → completion criteria → remaining work → decision validation
- **Cross-Session Learning**: Reflection insights → memory persistence → enhanced project understanding
## Examples
### Task Adherence Reflection
```
/sc:reflect --type task --analyze
# Validates current approach against project goals
# Identifies deviations and provides course correction recommendations
```
### Session Progress Analysis
```
/sc:reflect --type session --validate
# Comprehensive analysis of session work and information gathering
# Quality assessment and gap identification for project improvement
```
### Completion Validation
```
/sc:reflect --type completion
# Evaluates task completion criteria against actual progress
# Determines readiness for task completion and identifies remaining blockers
```
## Boundaries
**Will:**
- Perform comprehensive task reflection and validation using Serena MCP analysis tools
- Bridge TodoWrite patterns with advanced reflection capabilities for enhanced task management
- Provide cross-session learning capture and session lifecycle integration
**Will Not:**
- Operate without proper Serena MCP integration and reflection tool access
- Override task completion decisions without proper adherence and quality validation
- Bypass session integrity checks and cross-session persistence requirements