reflect · superclaude-org — Claude Code command: what it does, how to install
reflect evaluates task adherence and session progress using Serena MCP analysis tools. Useful for quality checks before marking tasks as complete.
MIT ★ 23,950 updated 2026-09-27
.claude/commands/reflect.mdWhat reflect does
The /sc:reflect command inspects task progress, checks requirement fulfillment, and tracks session metadata. It connects TodoRead and TodoWrite task patterns directly to Serena reflection tools, such as think_about_task_adherence for catching deviations and think_about_whether_you_are_done for verifying completion criteria.
For retaining context across work sessions, it executes read_memory and write_memory calls. The core reflection process is built to finish in under 200ms, while checkpoint creation takes less than 1s.
Serena MCP is mandatory here: the command will fail to run if those reflection tools are missing.
What it helps with
- validate task adherence against initial project goals
- verify completion criteria before closing a session
- persist learned insights across sessions using Serena memory
- detect blockers and work deviations during execution
Example prompts for the agent
- /sc:reflect --type task --analyze
- /sc:reflect --type session --validate
- /sc:reflect --type completion
How to install reflect
Manually: put the files in place
.claude/commands/reflect.mdCall it with /reflect. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/reflect.mdCall it with /prompts:reflect. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/reflect.prompt.mdManually: put the files in place
.gemini/commands/reflect.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about reflect
How to install reflect in Claude Code?
Add the command definition file to .claude/commands/reflect.md.
What does the reflect command do?
It runs reflection and quality checks against active tasks, verifying whether work meets requirements before wrapping up.
Does reflect require Serena MCP?
Yes, Serena MCP is required because the command relies directly on its reflection and memory tools.
Source text
reflect.md · MIT
--- 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
© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework
Similar slash commands
All slash commands for Agent setup: memory, context, orchestration →reflect by other authors comes first.